MTD Config.in items not escaped by bus availability

[Hicks, Jamey]

> -----Original Message-----
> From: Brian J. Murrell
> [mailto:8db422baa67bd7a698f50768bba0d47e at interlinx.bc.ca]
> Sent: Wednesday, October 30, 2002 3:50 PM
> To: linux-mtd at lists.infradead.org
> Cc: joern at wohnheim.fh-wedel.de; Hicks, Jamey
> Subject: Re: MTD Config.in items not escaped by bus availability
> 

> So the MTD subsystem will build and run on a UML (i.e. it has no
> hardware properties such as IRQ's, DMA, etc. itself)?  Surely there
> must be some aspect of the MTD system which becomes dependent on
> addressing specific hardware devices though?

I think that MTD can be built and run on UML.  Try these configuration options:
  CONFIG_MTD=y
  CONFIG_MTD_CHAR=m
  CONFIG_MTD_BLOCK=m
 
You can use system memory provided by vmalloc() for a test MTD device by enabling CONFIG_MTD_MTDRAM:
  CONFIG_MTDRAM=m

You can use a block device to provide a test MTD device with the blkmtd driver:
  CONFIG_MTD_BLKMTD=m

Neither of these virtual MTD devices depends on IRQ's, DMA, or other hardware resources.

-Jamey