MTD CVS update: 'mtd/kernel cfi_cmdset_0001.c cfi_probe.c nora.c octagon-5066.c vmax301.c'

[Jason Gunthorpe]

On Tue, 27 Jun 2000, David Woodhouse wrote:

> You've said, and I agree, that the map driver won't necessarily know the 
> size of the chips within the area, so it can't know how the aliases are 
> arranged and remap the space itself. 

The map driver is the only driver that knows what the eletrical connection
is, if it knows the banks are 4 meg apart then it has to communicate that
up. The only thing this is used for is detection, the detector can jump
to the next bank start and do all of the banks. The only other option is
to probe every block int the mapping region looking for bank starts, which
is gross since the information is available.

> Hmmm. How about a char * ?

That might be best.
 
> jgg at deltatee.com said:
> >  Should probably also use the named initializers the rest of the
> > kernel is moving to for these big structs.
> 
> You mean a static initialiser that ends up in the data segment rather than 
> kmalloc'd? What does it do for us?

No, the C99 named member initializers for structs:

struct foo = {name: "Hello",size: 1024};

Makes those big initializers readable.

Jason




To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org