From: arasv@magellan-technology.com (Aras Vaichas)
To: linux-arm-kernel@lists.infradead.org
Subject: cmpxchg() in recent kernels
Date: Tue, 26 Oct 2010 23:10:08 +1100 [thread overview]
Message-ID: <AANLkTin7B++tqimD2UK1bkhUS9QuCYmbch2QYMqAd8p4@mail.gmail.com> (raw)
In-Reply-To: <20101026064417.GM8554@pengutronix.de>
2010/10/26 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
> Hello Aras,
>
>> For reference, this is my uImage make script:
>>
>> make ARCH=arm CROSS_COMPILE=${CROSS_PATH} INSTALL_MOD_PATH=${FS_PATH} Image
>>
>> ${CROSS_PATH}objcopy -O binary -R .note -R .note.gnu.build-id -R
>> .comment -S vmlinux linux.bin
>
> Why don't you use arch/arm/boot/Image instead of doing the objcopy
> yourself? ?(If it's intended you might want to make vmlinux only instead
> of Image.)
My best guess is that it's carried over from my 2.4.x days.
A quick Google search shows several U-Boot image building tutorials
that do this.
e.g. http://www.ronetix.at/an008_ARM_Linux_Debugging.html
It was never a problem until GCC v4 was required for a clean kernel
build but I will certainly review my build scripts with this in mind.
:)
I only do kernel work every few years as needed for the company
product, so I tend to play catchups on these changes.
Aras
next prev parent reply other threads:[~2010-10-26 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 9:32 cmpxchg() in recent kernels Alex Sverdlin
2010-10-15 4:26 ` Aras Vaichas
2010-10-24 21:43 ` Kristoffer Ericson
2010-10-24 22:08 ` Russell King - ARM Linux
2010-10-25 1:33 ` Aras Vaichas
2010-10-25 6:37 ` Uwe Kleine-König
2010-10-25 15:13 ` Russell King - ARM Linux
2010-10-25 22:48 ` Aras Vaichas
2010-10-26 6:44 ` Uwe Kleine-König
2010-10-26 12:10 ` Aras Vaichas [this message]
2010-10-25 21:07 ` Kristoffer Ericson
2010-10-25 22:37 ` Alexander Sverdlin
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=AANLkTin7B++tqimD2UK1bkhUS9QuCYmbch2QYMqAd8p4@mail.gmail.com \
--to=arasv@magellan-technology.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).