cleaning up the Kconfig menu structure -- the bigger picture

[Dan Malek]

On Oct 8, 2004, at 3:48 PM, Tom Rini wrote:

> I don't get it.  We do agree that the very specific stuff does indeed
> belong somewhere that's obvious to the user, right?

I want all of the CPM and 8xx/82xx/85xx configuration to be in
a common menu, just like it is today.  I don't understand the
fascination with syslib/, but if that's where you want things,
that's fine.  Drivers that are common to multiple platforms or
otherwise interact with common subsystems (like uarts and
network drivers) should be in the standard directories.

As the discussion started out earlier today, I also don't like
the configuration options scattered about and in the past
we have discussed this was not to be the case.  Those of
us writing the new code or updating existing code all
thought this was the configuration process, and now today
you are arguing for something different and are likely to
implement it that way against our wishes.  Based upon the
processor type, we should be invoking different Kconfig
scripts that although may use the same sources have different
configuration option criteria.  It is significantly easier for
us to keep those things local for consistent modification,
and I contend will make it easier to focus on the configuration
selections when doing so interactively.

Thanks.


	-- Dan