MTD support for 8x16 devices

Alice Hennessy ahennessy at
Tue Aug 29 19:54:07 EDT 2000


 I am using the MTD driver  to accomodate two different products,  one  with
an AMD
and one  with an Intel Strata.   Both are the 8x16 variety.   I have several

1. The Strata is placed on the board as a byte wide device so I've added
another check in cfi_probe_new_chip() to try accessing the cfi ident info at
address 0xaa as well as the 0x55  (for buswidth of 1) and return an
"cfi_ident_adjustment" so that cfi_cfi_probe can correctly access the cfi
ident info (since the cfi ident field InterfaceDesc hasn't been read yet).
Is this an acceptable method to handle this?

2.  I've added code to support  1_by_8 functions in cfi_cmdset_0001.c for the
strata.  I've also added big endian and unaligned support in
cfi_amdext_write_2_by_16().   I've also added some support to handle different
erase sector sizes within one chip.  Has any of this already been checked in
recently?  And what is the procedure?

3.  For both products, I have made use of  my own combo of physmap.c and
nora.c so that the flash address and len can be set in menuconfig and the
flash can be partitioned.    It seems that this version of physmap.c can be
used in a very generic way if we also move buswidth into menuconfig.   I'm
also thinking about different ways for the partition sizes to be set outside
of physmap.c.   - any opinions?   Perhaps board specifics should be contained
in a header file and
be set via menuconfig or command line or ?

4.   I need to implement a char device where the customer wants to write to
the flash and have all the erase details handle by the driver.  They want to
simply do a dd into the device.  They don't need a file system
implementation.   Has there been any thought about doing this type of thing at
the driver level?


To unsubscribe, send "unsubscribe mtd" to majordomo at

More information about the linux-mtd mailing list