Re: MTD Config.in items not escaped by bus availability

["Brian J. Murrell" <6a127d328308423eb47c92a79d2841b6@interlinx.bc.ca>]

[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]

On Wed, Oct 30, 2002 at 11:22:50AM -0500, Hicks, Jamey wrote:
> 
> Some MTD devices connect directly to the CPU.  It seems to me that
> if you have a CPU with a memory bus, then it is possible to have MTD
> devices, so drivers/mtd/Config.in needs to give you the option of
> selecting those devices.

Hmmmm.  It would seem then that the kernel configuration system is
lacking a specification for a "memory bus".  Yes/No, what kind,
whatever.  But it is possible to build and run a kernel that does not
actually have a CPU or a memory bus, for example, in the case of a UML
kernel.

The UML configuration process does a good job of weeding out actual
hardware devices (in fact it's just the kernel configuration that does
the work), but it does that by nature of the configuation system
encapsulating hardware selection options (like MTD) inside bus
configuation.

> The MTD configuration is all wrapped with the toplevel CONFIG_MTD
> option, so there is really only one question you would have to say
> 'No' to in order to avoid the others.

True, but it would be nice if CONFIG_MTD were tied to some kind of
hardware (i.e. a memory bus) so that you could take a .config from a
real hardware running kernel and use it to build a UML kernel without
having to go and diddle with things like CONFIG_MTD.

b.

-- 
Brian J. Murrell

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]