LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@windriver.com>
To: "Paul Sokolovsky" <pmiscml@gmail.com>
Cc: "Lennert Buytenhek" <buytenh@wantstofly.org>,
"Michael K. Edwards" <medwards.linux@gmail.com>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>,
"Sam Ravnborg" <sam@ravnborg.org>,
linux-arm-toolchain@lists.arm.linux.org.uk,
linux-arm-kernel@lists.arm.linux.org.uk, crossgcc@sourceware.org
Subject: Re: Re[2]: More ARM binutils fuckage
Date: Wed, 6 Dec 2006 09:37:43 -0500 [thread overview]
Message-ID: <3bd6b93c0612060637g2c6f4b5bld4006b40244a7b06@mail.gmail.com> (raw)
In-Reply-To: <582252003.20061206084328@gmail.com>
On 12/6/06, Paul Sokolovsky <pmiscml@gmail.com> wrote:
> Hello Lennert,
>
> Wednesday, December 6, 2006, 3:08:13 AM, you wrote:
>
> []
> > (These
> > days I build all kernels in EABI mode with old-ABI compat.) I have
> > not run into any code generation issues with this compiler yet.
>
> I wonder, if OABI-compat is known to actually work on OABI userspace,
> I mean, on something real, like xserver-kdrive ;-). Because I'd really
> like to build single kernel for both old and new userspace too, but
> afraid to try that, fearing to be put down by another broken feature
> ;-).
I've used OABI-compat + EABI ARM kernels to routinely switch between
OABI and EABI rootfs boots. There were some minor busybox issues
on the OABI-compat side (w.r.t. syscalls), but nothing major. These
were fairly complex applications, so "it should work" (and IIRC the
patches were publicly available). But I'm sure I'm forgetting some
significant detail and can't go check right now.
>
>
> --
> Best regards,
> Paul mailto:pmiscml@gmail.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
next prev parent reply other threads:[~2006-12-06 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 19:33 Russell King
2006-12-05 23:29 ` Michael K. Edwards
2006-12-06 0:22 ` Russell King
2006-12-06 1:08 ` Lennert Buytenhek
2006-12-06 6:43 ` Re[2]: " Paul Sokolovsky
2006-12-06 8:17 ` Koen Kooi
2006-12-06 14:37 ` Bruce Ashfield [this message]
2006-12-06 1:34 ` Michael K. Edwards
2006-12-06 0:25 ` Russell King
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=3bd6b93c0612060637g2c6f4b5bld4006b40244a7b06@mail.gmail.com \
--to=bruce.ashfield@windriver.com \
--cc=buytenh@wantstofly.org \
--cc=crossgcc@sourceware.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-arm-toolchain@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=medwards.linux@gmail.com \
--cc=pmiscml@gmail.com \
--cc=sam@ravnborg.org \
--subject='Re: Re[2]: More ARM binutils fuckage' \
/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
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).