From: Tom Rini <trini@kernel.crashing.org>
To: Michael Sokolov <msokolov@ivan.Harhan.ORG>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt
Date: Tue, 9 Apr 2002 07:52:22 -0700 [thread overview]
Message-ID: <20020409145222.GB710@opus.bloom.county> (raw)
In-Reply-To: <0204081705.AA21087@ivan.Harhan.ORG>
On Mon, Apr 08, 2002 at 10:05:53AM -0700, Michael Sokolov wrote:
>
> Tom Rini <trini@kernel.crashing.org> wrote:
>
> > We shouldn't be #ifdef'ing externs, since it doesn't matter. The
> > pmac/prep/chrp ones were hidden just because the line above was, iirc.
>
> OK.
>
> > And the one downside to the GENERIC_PPC32 platform_init, is that we're
> > back to adding:
> > #ifdef CONFIG_x
> > case _MACH_x:
> > x_init(...);
> > break;
> > #endif
>
> And what's wrong with that? It allows the user to make the kernel size vs.
> generality trade-off: you can have one machine supported or all of them.
Well, take a look at what the file used to look like in _devel. It was
around 30-40 lines of that. Which is not nice to look at.
> > Which I think Paul was happy to see die :)
>
> But it's necessary, and it's a much better system than what you have now.
Well, it's a much better system if you want to group unlike hardware
together in one kernel. :)
> > > arch/ppc/config.in
> > > 1.127 02/03/31 23:58:43 msokolov@helium.harhan.org +18 -21
> > > Add generic PPC32 config, implemented for
> > > Adirondack, EV-64260A, and K2
> >
> > Do any of these boards actually have an ISA slot?
>
> The boards I've used for this first implementation don't. But
> CONFIG_GENERIC_PPC32 is generic PPC32, not just these boards, and it should be
> possible for someone to support a machine with ISA slots under this generic
> framework.
Well, if ISA slots exist on the board, and should be working, they
should just work. And when BenH merges in prep/chrp, it'll be needed.
But the question is do you really want to offer this up on machines
where it's not tested?
> > Right now it's an ALL_PPC-only
> > option because it's actually needed for sound on some PReP boxes..
>
> And I'm hoping that some day PReP will be part of CONFIG_GENERIC_PPC32. See
> BenH's response about putting CONFIG_ALL_PPC to rest and converting to
> CONFIG_GENERIC_PPC32.
Right.
--
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-09 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200204060739.g367duV18841@helium.Harhan.ORG>
2002-04-08 15:20 ` Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt Tom Rini
2002-04-08 17:58 ` benh
2002-04-08 18:57 ` Tom Rini
2002-04-08 18:40 ` Benjamin Herrenschmidt
2002-04-09 8:14 ` Geert Uytterhoeven
2002-04-09 10:08 ` benh
[not found] ` <0204081705.AA21087@ivan.Harhan.ORG>
2002-04-08 18:02 ` benh
2002-04-09 14:52 ` Tom Rini [this message]
2002-04-09 19:23 ` Michael Sokolov
2002-04-09 19:47 ` Tom Rini
2002-04-09 20:05 ` Michael Sokolov
2002-04-09 20:15 ` Daniel Jacobowitz
2002-04-10 15:09 ` Tom Rini
2002-04-11 3:11 ` Michael Sokolov
2002-04-11 15:29 ` Tom Rini
2002-04-15 16:54 ` Troy Benjegerdes
2002-04-15 18:11 Michael Sokolov
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=20020409145222.GB710@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=msokolov@ivan.Harhan.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