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 12:47:21 -0700 [thread overview]
Message-ID: <20020409194721.GI1331@opus.bloom.county> (raw)
In-Reply-To: <0204091923.AA23957@ivan.Harhan.ORG>
On Tue, Apr 09, 2002 at 12:23:57PM -0700, Michael Sokolov wrote:
>
> Tom Rini <trini@kernel•crashing.org> wrote:
>
> > 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.
>
> So what's more important, a pretty look or better functionality for the user?
>
> > Well, it's a much better system if you want to group unlike hardware
> > together in one kernel. :)
>
> Which is what I want to do, and which is the RTTD for distributions like
> Debian.
Taking debian as an example here. You certainly wouldn't stick a zImage
for every board into 1 package. Why? It'd be a 20mb package and as it
is a few people dislike the number of vmlinux's in the -pmac package.
So you only 'win' if you have a common, _bootable_ image on all of these
boards. And while it is possible that there could be a common
firmware, I'm not holding my breath. :)
And the other point is that this makes it less clean to add in a new
board port.
> > 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?
>
> I want to have configurable CONFIG_PCI and CONFIG_ISA support for
> CONFIG_GENERIC_PPC32. Generic means that things like this must be
> configurable.
But what if they aren't really configurable? You could turn off
CONFIG_PCI, but I don't think you'd get too far on most[1] systems.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
[1]: Most, not all, most. I know there's 8xx and others...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-09 19:47 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
2002-04-09 19:23 ` Michael Sokolov
2002-04-09 19:47 ` Tom Rini [this message]
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=20020409194721.GI1331@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