From: Tom Rini <trini@kernel•crashing.org>
To: Michael Sokolov <msokolov@ivan•Harhan.ORG>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: The very common kernel, again...
Date: Thu, 11 Apr 2002 10:46:55 -0700 [thread overview]
Message-ID: <20020411174655.GD19157@opus.bloom.county> (raw)
In-Reply-To: <0204111731.AA29012@ivan.Harhan.ORG>
On Thu, Apr 11, 2002 at 10:31:13AM -0700, Michael Sokolov wrote:
>
> Tom Rini <trini@kernel•crashing.org> wrote:
>
> > Why? Why is it a good thing to put this into 'CONFIG_ALL_PPC' ? You
> > still end up with 3 images (PReP, vmlinux for pmac/chrp, PPCStar) which
> > I wouldn't think is any worse from N (either the FW lets you load an
> > abitrary kernel off of the CD/HD/whatever, or you have to put on the
> > !vmlinux (in CONFIG_ALL_PPC's case, yaboot) booting kernel else-where.
>
> But we wouldn't have this mess if you guys would just let us have one
> CONFIG_GENERIC_PPC32 vmlinux with a standardized and stable boot ABI. Then we,
> the people with incentive to sell boards, would do what we need to do with our
> firmware or booters or whatever to boot that standard vmlinux and make it as
> easy as possible for people like Debian to support us in the standard dist.
This has _nothing_ to do with the boot ABI. The boot ABI for 2.4 hasn't
changed, as far as I can remember anyhow. The plan for 2.5 is to come
up with and agree upon once and for all (and it seems that it's been
mostly done too). The question I asked is why do you want to make a
vmlinux that runs on large groups of totally unrelated, save for a CPU
family, mostly, group of computers.
If someone really wanted, they could put 8xx and 4xx into this mess too,
with some complex asm, and have 1 kernel that boots on 4xx/6xx/7xx/74xx/8xx.
I doubt it'd be useful, but it could be done.
>
> MS
>
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-11 17:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 20:23 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-06 22:06 ` CONFIG_GENERIC_PPC32 Benjamin Herrenschmidt
2002-04-08 15:48 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-08 16:03 ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 16:24 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-08 16:48 ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 17:23 ` CONFIG_GENERIC_PPC32 Matt Porter
2002-04-08 17:37 ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 18:07 ` CONFIG_GENERIC_PPC32 Matt Porter
2002-04-08 18:41 ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 18:18 ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-08 18:53 ` CONFIG_GENERIC_PPC32 Matt Porter
2002-04-09 14:59 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-09 19:52 ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-10 8:27 ` CONFIG_GENERIC_PPC32 Geert Uytterhoeven
2002-04-10 15:17 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11 3:50 ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 15:27 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-10 10:28 ` Bootloader (Re: CONFIG_GENERIC_PPC32) benh
2002-04-10 13:30 ` Dan Malek
2002-04-10 15:16 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11 3:46 ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 15:24 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11 16:16 ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 15:51 ` CONFIG_GENERIC_PPC32 Mark A. Greer
2002-04-11 16:59 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11 17:25 ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 17:42 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11 17:03 ` The very common kernel, again... (Was: Re: CONFIG_GENERIC_PPC32) Tom Rini
2002-04-11 17:31 ` The very common kernel, again Michael Sokolov
2002-04-11 17:46 ` Tom Rini [this message]
2002-04-10 19:08 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-10 13:20 ` CONFIG_GENERIC_PPC32 Paul Mackerras
2002-04-10 15:23 ` CONFIG_GENERIC_PPC32 benh
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=20020411174655.GD19157@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=msokolov@ivan$(echo .)Harhan.ORG \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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