linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: cleaning up the Kconfig menu structure -- the bigger picture
Date: Fri, 8 Oct 2004 09:40:47 -0700	[thread overview]
Message-ID: <20041008164047.GC14773@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0410080704170.6219@dell.enoriver.com>

On Fri, Oct 08, 2004 at 07:16:18AM -0400, Robert P. J. Day wrote:

>   somewhat related to dan malek's posting, but i think part of the 
> problem with trying to figure out what the menuconfig menus should 
> support is that the relevant options are organized in a confusingly 
> haphazard way.

I suppose it's confusing from how it used to be, but not so much from a
how everyone else chooses stuff way.  For example...
[snip]
>   consider, first, serial port options.  if you choose 8xx, then 
> you'll be presented with the menu choices:
> 
>   Device Drivers -->
>     Character devices -->
>       Serial drivers -->
>         CPM SCC/SMC serial port support --> etc, etc.

Which is where every other serial driver is (that's been updated to use
the new serial core and make life easier).

[snip]
>   in that case, if you wanted to configure "CPM SCC Ethernet", why 
> would you go under "MPC8xx CPM Options" rather than the general 
> networking menu?  this is clearly inconsistent.

Because the CPM1/CPM2 enet drivers are still waiting to be cleaned up a
bit more, and moved there.  The FEC enet driver that Pantelis wrote
lives in drivers/net/ for example.

>   more to the point, i've always found it a bit strange that selecting 
> "8xx" as a processor would suddenly cause the top-level "MPC8xx CPM 
> Options" menu to appear, when other 8xx-related stuff was still 
> scattered elswewhere throughout the kernel source tree.

That's kinda the opposite direction of where I want things to move.
What, IMHO, should happen is that once the real drivers side of 8xx_io
are moved out into drivers/ we'll really be left with commproc and
microcode, both of which can live in arch/ppc/syslib/ as cpm1_common.c
and cpm1_microcode.c respecivley and we can deal with microcode
questions in arch/ppc/Kconfig where we now source the 8xx_io/Kconfig
file (or, if it really does end up making sense to, and I'm not yet
convinced of this, make platforms/8xx, we can put the question in
platforms/8xx/Kconfig).

-- 
Tom Rini
http://gate.crashing.org/~trini/

  parent reply	other threads:[~2004-10-08 16:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 11:16 cleaning up the Kconfig menu structure -- the bigger picture Robert P. J. Day
2004-10-08 15:31 ` Dan Malek
2004-10-08 15:38   ` Robert P. J. Day
2004-10-08 16:37     ` Dan Malek
2004-10-08 16:31       ` Robert P. J. Day
2004-10-08 16:40 ` Tom Rini [this message]
2004-10-08 16:42   ` Robert P. J. Day
2004-10-08 17:22   ` Dan Malek
2004-10-08 18:02     ` Tom Rini
2004-10-08 18:39       ` Dan Malek
2004-10-08 19:48         ` Tom Rini
2004-10-08 20:49           ` Dan Malek
2004-10-08 21:38             ` Tom Rini
2004-10-08 22:03             ` Wolfgang Denk

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=20041008164047.GC14773@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rpjday@mindspring.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).