Flash driver probe/commandset separation.

Eric W. Biederman ebiederman at lnxi.com
Thu May 3 17:45:52 EDT 2001


David Woodhouse <dwmw2 at infradead.org> writes:

> ebiederman at lnxi.com said:
> >  Note there is a good argument for joining the probe paths Handling
> > chip interleaving, unless we can make it simple we don't want that
> > duplicated many times.
> 
> True. The build_cmd et al macros prevent duplication to a certain extent. 
> 
> > I'll try to have something working for 2 & 4 by the end of today.  Any
> > hints on why the cmdset drivers don't compile? 
> 
> I changed the chip driver registration stuff. They need to have a 
> struct mtd_chip_driver and set mtd->fldrv to point to it. 

I'll look I currently have the simply moved the destroy function into
cfi_probe.  

> And I'd like to 
> make the inter_module_xxx stuff go away completely - maybe they can 
> register with the code in chipreg instead, and get cfi_probe to look them 
> up that way. That can wait a little while though - I'm not sure that's the 
> correct approach (because they're not actually probes).

Right, but something smiliar code work.  Or we could make them serve
dual duty.  

Eric




More information about the linux-mtd mailing list