From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Bernhard Reiter <bernhard@intevation.de>,
debian-powerpc@lists.debian.org, paulus@samba.org
Subject: Re: compile quirk linux-2.6.24 (with workaround)
Date: Tue, 5 Feb 2008 08:24:38 -0700 [thread overview]
Message-ID: <fa686aa40802050724o692ef9e7yf51945225f56da5b@mail.gmail.com> (raw)
In-Reply-To: <20080205091548.724c4e20@zod.rchland.ibm.com>
On 2/5/08, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> > I mean, if you have not included 4xx support in the kernel, as is the
> > case here, it does not make sense to add the 4xx bootwrapper code, no ?
>
> It does, in a manner. There are both generic and platform specific
> pieces to the bootwrapper. Having everything always built helps keep
> the generic bits from breaking, which is important as they're often
> tightly coupled. That's at least the reason I can think of.
>
> The powerpc maintainers have been over this quite a bit and I don't see
> it changing anytime soon.
That would mean we're dropping support for compilers which can't build
405/440 specific wrapper bits (or other core specific quirks that need
to go in the wrapper) That doesn't sound appropriate to me.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-02-05 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 16:29 compile quirk linux-2.6.24 (with workaround) Bernhard Reiter
2008-02-04 9:51 ` Sven Luther
2008-02-04 10:26 ` Bernhard Reiter
2008-02-04 17:34 ` Grant Likely
2008-02-05 13:08 ` Josh Boyer
2008-02-05 14:39 ` Sven Luther
2008-02-05 15:15 ` Josh Boyer
2008-02-05 15:24 ` Grant Likely [this message]
2008-02-05 15:38 ` Josh Boyer
2008-02-05 16:10 ` Olof Johansson
2008-02-06 10:07 ` Bernhard Reiter
2008-02-19 2:52 ` Josh Boyer
2008-02-22 14:50 ` Bernhard Reiter
2008-02-25 11:56 ` Bernhard Reiter
2008-03-03 17:26 ` Bernhard Reiter
2008-02-04 21:01 ` Josh Boyer
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=fa686aa40802050724o692ef9e7yf51945225f56da5b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=bernhard@intevation.de \
--cc=debian-powerpc@lists.debian.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).