From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] Automate uboot entry/load addresses detection.
Date: Tue, 03 Feb 2009 12:31:44 +0100 [thread overview]
Message-ID: <gm99v0$ier$1@ger.gmane.org> (raw)
In-Reply-To: <fce2a370902030302m1054bfc5wc5589ed60418c959@mail.gmail.com>
On 03-02-09 12:02, Ihar Hrachyshka wrote:
> Any chances for inclusion?
It looks pretty good to me, but I'd like to hear from people that tested
it :)
regards,
Koen
> On Fri, Jan 30, 2009 at 2:37 PM, Ihar Hrachyshka
> <ihar.hrachyshka@gmail.com> wrote:
>> Automated UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT variables detection (no
>> need to specify them for every machine and/or kernel now).
>>
>> Signed-off-by: Ihar Hrachyshka<ihar.hrachyshka@gmail.com>
>> ---
>> classes/kernel.bbclass | 8 ++++----
>> 1 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/classes/kernel.bbclass b/classes/kernel.bbclass
>> index d1f59e5..f7a7014 100644
>> --- a/classes/kernel.bbclass
>> +++ b/classes/kernel.bbclass
>> @@ -69,10 +69,6 @@ KERNEL_LOCALVERSION ?= ""
>> # kernels are generally machine specific
>> PACKAGE_ARCH = "${MACHINE_ARCH}"
>>
>> -# U-Boot support
>> -UBOOT_ENTRYPOINT ?= "20008000"
>> -UBOOT_LOADADDRESS ?= "${UBOOT_ENTRYPOINT}"
>> -
>> kernel_do_compile() {
>> if [ ! -z "${INITRAMFS_IMAGE}" ]; then
>> cp "${DEPLOY_DIR_IMAGE}/${INITRAMFS_IMAGE}-${MACHINE}.cpio.gz" initramfs.cpio.gz
>> @@ -489,12 +485,16 @@ do_deploy() {
>> if test "x${KERNEL_IMAGETYPE}" = "xuImage" ; then
>> if test -e arch/${ARCH}/boot/compressed/vmlinux ; then
>> ${OBJCOPY} -O binary -R .note -R .comment -S arch/${ARCH}/boot/compressed/vmlinux linux.bin
>> + UBOOT_LOADADDRESS=`${OBJDUMP} -p arch/${ARCH}/boot/compressed/vmlinux | sed -n 's/LOAD.*vaddr \([^ ]*\).*/\1/p'`; \
>> + UBOOT_ENTRYPOINT=`${OBJDUMP} -f arch/${ARCH}/boot/compressed/vmlinux | sed -n 's/.*start address \([^ ]*\).*/\1/p'`; \
>> uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C none -a ${UBOOT_LOADADDRESS} -e ${UBOOT_ENTRYPOINT} -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE_BASE_NAME}.bin
>> rm -f linux.bin
>> else
>> ${OBJCOPY} -O binary -R .note -R .comment -S vmlinux linux.bin
>> rm -f linux.bin.gz
>> gzip -9 linux.bin
>> + UBOOT_LOADADDRESS=`${OBJDUMP} -p vmlinux | sed -n 's/LOAD.*vaddr \([^ ]*\).*/\1/p'`; \
>> + UBOOT_ENTRYPOINT=`${OBJDUMP} -f vmlinux | sed -n 's/.*start address \([^ ]*\).*/\1/p'`; \
>> uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C gzip -a ${UBOOT_LOADADDRESS} -e ${UBOOT_ENTRYPOINT} -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin.gz ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE_BASE_NAME}.bin
>> rm -f linux.bin.gz
>> fi
>> --
>> 1.5.6.3
>>
>>
>>
next prev parent reply other threads:[~2009-02-03 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 12:37 [PATCH] Automate uboot entry/load addresses detection Ihar Hrachyshka
2009-01-30 12:57 ` Graeme Gregory
2009-02-03 11:02 ` Ihar Hrachyshka
2009-02-03 11:31 ` Koen Kooi [this message]
2009-03-03 15:55 ` Ihar Hrachyshka
2009-03-29 22:28 ` Andrea Adami
2009-03-29 22:35 ` [PATCH] kernel.bbclass: " Andrea Adami
2009-03-29 22:58 ` [PATCH] " Ihar Hrachyshka
2009-03-29 23:11 ` Andrea Adami
2009-03-29 23:32 ` Andrea Adami
2009-07-03 14:30 ` Ihar Hrachyshka
2009-07-03 22:25 ` Andrea Adami
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='gm99v0$ier$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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