From: "H. J. Lu" <hjl@lucon.org>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: PATCH: Use .incbin to incorporate binary files.
Date: Wed, 11 Jun 2003 15:49:51 -0700 [thread overview]
Message-ID: <20030611224951.GA1060@lucon.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
The Linux binutils 2.11.90.0.23 released on 2001-07-14 introduced
a new feature, .incbin, which allows you to include a set of binary
data at a given point in the assembly. It is better than
# ld -r --format binary --oformat ...
since it will set appropriate bits in the ELF header. Here is a patch
against 2.5.70 to use .incbin.
H.J.
[-- Attachment #2: binary.patch --]
[-- Type: text/plain, Size: 880 bytes --]
--- linux/usr/Makefile.binary Mon Mar 24 14:00:45 2003
+++ linux/usr/Makefile Wed Jun 11 15:44:23 2003
@@ -5,11 +5,9 @@ host-progs := gen_init_cpio
clean-files := initramfs_data.cpio.gz
-LDFLAGS_initramfs_data.o := $(LDFLAGS_BLOB) -r -T
-
-$(obj)/initramfs_data.o: $(src)/initramfs_data.scr \
- $(obj)/initramfs_data.cpio.gz FORCE
- $(call if_changed,ld)
+$(src)/initramfs_data.S: $(obj)/initramfs_data.cpio.gz
+ echo " .section .init.ramfs,\"a\"" > $(src)/initramfs_data.S
+ echo ".incbin \"usr/initramfs_data.cpio.gz\"" >> $(src)/initramfs_data.S
# initramfs-y are the programs which will be copied into the CPIO
# archive. Currently, the filenames are hardcoded in gen_init_cpio,
--- linux/usr/initramfs_data.scr.binary Mon Mar 24 14:00:11 2003
+++ linux/usr/initramfs_data.scr Wed Jun 11 15:44:32 2003
@@ -1,4 +0,0 @@
-SECTIONS
-{
- .init.ramfs : { *(.data) }
-}
reply other threads:[~2003-06-11 22:37 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=20030611224951.GA1060@lucon.org \
--to=hjl@lucon.org \
--cc=linux-kernel@vger.kernel.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