MTD Config.in items not escaped by bus availability

[David Woodhouse]

e88cd5ffd87e620fdc30b3e6db510d03 at interlinx.bc.ca said:
>  I hope I am understanding the question/scenario you are proposing,
> but the answer seems to simple, so I am sure I am missing something.

> When/if someone makes that UML mapping driver, it would have it's

<PEDANT>
	YM "its"
</PEDANT>

(Sorry, customers being bloody stupid at me today and I have to be nasty to 
_someone_ or my brain will explode :)

> CONFIG_MTD_UML (or whatever they will call it) outside of the
> CONFIG_MEMORY bus protected portions of the MTD Config.in files.

But the options for the _chips_ it's able to find in that mapping are 
disabled because CONFIG_MEMORY_BUS is turned off.

A better plan would be to allow the chip configuration to be enabled iff 
there is at least one mapping driver enabled. 

--
dwmw2