From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: h3600: update defconfig
Date: Wed, 2 Oct 2013 21:56:04 +0100 [thread overview]
Message-ID: <20131002205604.GX12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAAQYJAtWf9UYW3Zxmd+4gW-8aPtWyT0kNqCfRO5MNT_5ig4qCg@mail.gmail.com>
On Wed, Oct 02, 2013 at 10:47:41PM +0200, Andrea Adami wrote:
> On Wed, Oct 2, 2013 at 10:32 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Mon, Sep 30, 2013 at 11:19:54AM +0200, Linus Walleij wrote:
> >> This updates the h3600 defconfig against the latest kernel with
> >> some small options coming and going due to Kconfig structure,
> >> then modernize it to:
> >>
> >> - Use EABI to compile the kernel
> >
> > EABI on ARMv4 *non-T* and without --fix-v4bx (a) added to the linker
> > arguments, and (b) V4BX relocations added to the kernel module loader?
> > Are you sure this is all that's required?
> >
>
> Yes, the toolchain built with OpenEmbedded / Yocto Project contains
> the necessary fixes [1] since end 2012.
> Runtime tested eglibc and klibc on Zaurus collie.
> Same binaries even tested on armv5te.
>
> [1] http://cgit.openembedded.org/openembedded-core/log/?qt=grep&q=armv4
Sorry, I don't accept this as an adequate "fix" for the kernel. It's not
up to the build environment to provide --fix-v4bx to the kernel makefiles
to work around this problem. That's just the sticky plaster fix and not
proper engineering.
prev parent reply other threads:[~2013-10-02 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 9:19 [PATCH] ARM: h3600: update defconfig Linus Walleij
2013-10-02 20:32 ` Russell King - ARM Linux
2013-10-02 20:47 ` Andrea Adami
2013-10-02 20:56 ` Russell King - ARM Linux [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=20131002205604.GX12758@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).