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

Matt Sealey wrote:
>> CHRP and PMAC aren't following the rules that everyone else is 
>> following.  Why?
> 
> Because they are by far the historically most common configuration, and
> still in production as the defacto standard PowerPC system configuration.

So you could make an argument for it being turned on in 
arch/powerpc/defconfig, if we had one.  That doesn't mean it should be 
"default y".

> 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,

What do distributions have to do with it?  It's harder for distributions 
to set the options they want than for embedded developers?

> 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).

Likewise there's no reason that PMAC/CHRP can't be DISABLED by default, 
and turned on by YOU.

> 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,

s/a bit/a lot/

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

Really?  Who do I go to for this guarantee, when there's no support for 
the hardware I'm trying to get to work? :-)

-Scott

  reply	other threads:[~2008-10-10  9:26 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 [this message]
2008-10-09 17:23               ` Timur Tabi
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=48EE3A9D.5040007@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    --cc=timur@freescale.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).