From: Brian Gerst <bgerst@quark.didntduck.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, kai.germaschewski@unh.edu
Subject: [PATCH] Delete initramfs_data.S.tmp
Date: Fri, 08 Aug 2003 12:30:50 -0400 [thread overview]
Message-ID: <3F33D03A.7010705@quark.didntduck.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 94 bytes --]
This file was added to BK recently but as far as I can tell isn't needed.
--
Brian Gerst
[-- Attachment #2: initramfstmp-1 --]
[-- Type: text/plain, Size: 1299 bytes --]
diff -urN linux-2.6.0-test2-bk/initramfs_data.S.tmp linux/initramfs_data.S.tmp
--- linux-2.6.0-test2-bk/initramfs_data.S.tmp 2003-08-08 08:02:50.714038376 -0400
+++ linux/initramfs_data.S.tmp 1969-12-31 19:00:00.000000000 -0500
@@ -1,30 +0,0 @@
-/*
- initramfs_data includes the compressed binary that is the
- filesystem used for early user space.
- Note: Older versions of "as" (prior to binutils 2.11.90.0.23
- released on 2001-07-14) dit not support .incbin.
- If you are forced to use older binutils than that then the
- following trick can be applied to create the resulting binary:
-
-
- ld -m elf_i386 --format binary --oformat elf32-i386 -r \
- -T initramfs_data.scr initramfs_data.cpio.gz -o initramfs_data.o
- ld -m elf_i386 -r -o built-in.o initramfs_data.o
-
- initramfs_data.scr looks like this:
-SECTIONS
-{
- .init.ramfs : { *(.data) }
-}
-
- The above example is for i386 - the parameters vary from architectures.
- Eventually look up LDFLAGS_BLOB in an older version of the
- arch/$(ARCH)/Makefile to see the flags used before .incbin was introduced.
-
- Using .incbin has the advantage over ld that the correct flags are set
- in the ELF header, as required by certain architectures.
-*/
-
-.section .init.ramfs,"a"
-.incbin "usr/initramfs_data.cpio.gz"
-
reply other threads:[~2003-08-08 16:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F33D03A.7010705@quark.didntduck.org \
--to=bgerst@quark.didntduck.org \
--cc=kai.germaschewski@unh.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®