From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v2] SPARC: added U-Boot build target: uImage
Date: Wed, 26 Jan 2011 15:40:40 +0000 [thread overview]
Message-ID: <4D404078.4020108@gaisler.com> (raw)
In-Reply-To: <1294674552-26656-1-git-send-email-daniel@gaisler.com>
Sam Ravnborg wrote:
>Hi Daniel.
>
>Looks better...
>
>
>
>> define archhelp
>> echo '* image - kernel image ($(boot)/image)'
>> echo '* zImage - stripped kernel image ($(boot)/zImage)'
>>+ echo ' uImage - U-Boot SPARC32/LEON Image'
>> echo ' tftpboot.img - image prepared for tftp'
>>
>>
>
>On the commandline you use "sparc32" - so to be consistent I think we should
>use "sparc32" in the help text too. But I do not feel strong about this at all.
>
>
>
>
>>+OBJCOPYFLAGS_image.bin := -S -O binary -R .note -R .comment
>>+$(obj)/image.bin: $(obj)/image FORCE
>>+ $(call if_changed,objcopy)
>>
>>
>
>I recall that we remove .note in similar places.
>Could you double check what other archs do here.
>
>
It seems to me that x86 also removes .note when making bin format.
>
>
>>+
>>+$(obj)/image.gz: $(obj)/image.bin
>>+ $(call if_changed,gzip)
>>+
>>+# Start of Main memory which this Linux kernel will be loaded to.
>>+ifndef CONFIG_UBOOT_LOAD_ADDR
>>+CONFIG_UBOOT_LOAD_ADDR=0x40004000
>>+endif
>>
>>
>
>I do not see that value in testign for the three newly introduced
>Kconfig symbols.
>In your backported kernel it may make sense but in mainline the symbols
>will always be defined as Kconfig define them.
>
>So just reference them direct.
>
>
Good point, see new patch.
Thanks,
Daniel
prev parent reply other threads:[~2011-01-26 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 15:49 [PATCH v2] SPARC: added U-Boot build target: uImage Daniel Hellstrom
2011-01-10 16:17 ` Sam Ravnborg
2011-01-26 15:40 ` Daniel Hellstrom [this message]
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=4D404078.4020108@gaisler.com \
--to=daniel@gaisler.com \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.