linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Timur Tabi" <timur@freescale.com>
To: "Matt Sealey" <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: remove default=y from PMAC and CHRP Kconfigs
Date: Thu, 9 Oct 2008 12:23:06 -0500	[thread overview]
Message-ID: <ed82fe3e0810091023j5f746a9cs7f8564c1e6ea8dcb@mail.gmail.com> (raw)
In-Reply-To: <48EE3636.7020305@genesi-usa.com>

On Thu, Oct 9, 2008 at 11:49 AM, Matt Sealey <matt@genesi-usa.com> wrote:
> Because they are by far the historically most common configuration, and
> still in production as the defacto standard PowerPC system configuration.

Not really.  PMAC systems are not being built any more.  So that leaves CHRP.

> IBM blades etc. with SLOF will boot up as a CHRP-ish system, as well as the
> Efika and Pegasos and anything else Genesi produces. Since Linux
> distributions generally do not support tiny embedded boards,

So what?  Distributions don't need our help to turn on the options
that are important to them.  This is a ridiculous argument.

> you can imagine why it's
> disabled by default, but there's no reason it can't be ENABLED by default
> and turned off by a distribution, the same way it can't be enabled by
> default and turned off by YOU (compare and contrast having to manually
> select which board you want to build for every time).

This problem is solved with defconfigs.  Kconfig options are supposed
to make sense.  Not all PowerPC systems are CHRP, therefore CHRP
should not be enabled by default.

> But, turning them all on would not matter. You would build a kernel for
> every one and a device tree for every one increasing your build time a
> bit for a default kernel,

Not really true.  Having the default be disabled for specific
platforms can make a big difference in compile time.

> but you would be guaranteed to get a kernel
> binary somewhere in the tree that would work on all of them :)

Again, not relevant.  One giant kernel that works on a Freescale
embedded system *and* an IBM mainframe is useless.  No one would
actually ever do that.

> Genesi, Manager, Developer Relations

Developer Relations, eh?

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2008-10-09 17:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 19:57 [PATCH] powerpc: remove default=y from PMAC and CHRP Kconfigs Timur Tabi
2008-10-08 20:03 ` Benjamin Herrenschmidt
2008-10-08 20:14   ` Timur Tabi
2008-10-08 20:39     ` Benjamin Herrenschmidt
2008-10-08 20:44       ` Timur Tabi
2008-10-09 15:59         ` Matt Sealey
2008-10-09 16:20           ` Timur Tabi
2008-10-09 16:49             ` Matt Sealey
2008-10-09 17:08               ` Scott Wood
2008-10-09 17:23               ` Timur Tabi [this message]
2008-10-09 20:18                 ` Sven Luther
2008-10-09 21:14                   ` Timur Tabi
2008-10-09 21:28                     ` Sven Luther
2008-10-09 21:32                       ` Timur Tabi
2008-10-10  0:43             ` Paul Mackerras
2008-10-10  1:22               ` Kumar Gala
2008-10-10  1:51                 ` Timur Tabi
2008-10-10  3:01                   ` Benjamin Herrenschmidt
2008-10-10  3:01                 ` Benjamin Herrenschmidt
2008-10-09 16:21           ` Scott Wood
2008-10-08 20:46   ` Scott Wood

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=ed82fe3e0810091023j5f746a9cs7f8564c1e6ea8dcb@mail.gmail.com \
    --to=timur@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    /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).