AM29DL16x series driver
Quoted 12 lines · --- Alexander Larsson
Quoted 3 lines · Marco A. Moreno
Hi,
I'm working on a project that is slated to use the 'DL162 and 'DL163 AMD
parts.
Quoted 1 line
I saw in the archives that someone wrote an 'LV160 driver. I want to know
if
Quoted 1 line
there would be significant changes to the driver to support the DL parts
which
Quoted 9 lines
Quoted 3 lines
differ in that they have flexible sectors. Does the CFI take care of this?
Any info would be greatly appreciated.
What do you mean by "flexible sectors"? The driver can handle flash chips with erase sectors of different sizes.
/ Alex
Sorry about that, it's not the 16x parts that have what AMD calls the "Flexible Sector Achitecture", it's the 800 parts. There's a comment in the mtd memory mapped code that says that the 800 parts aren't supported. Now that I've taken a closer look, I don't think that the amd_flash driver even depends on the memory mapped code. Is this true?
What I really meant to say was that it looks like the big difference between the lv160 and the dl162/163 is that the 162/163 supports simultaneous read/write capability. It doesn't seem like this feature would warrant a driver change. Besides, if the kernel runs from RAM, then this feature never gets used after the kernel is booted. So, does anyone see any reason why the lv160 driver wouldn't work for the dl162/163 chips?
Marco
=====
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
To unsubscribe, send "unsubscribe mtd" to [email protected]
Quoted 4 lines · Marco A. Moreno
Quoted 3 lines · --- Alexander Larsson
What do you mean by "flexible sectors"? The driver can handle flash chips with erase sectors of different sizes.
Quoted 8 lines
Quoted 2 lines
/ Alex
Sorry about that, it's not the 16x parts that have what AMD calls the "Flexible Sector Achitecture", it's the 800 parts. There's a comment in the mtd memory mapped code that says that the 800 parts aren't supported. Now that I've taken a closer look, I don't think that the
amd_flashdriver even depends on the memory mapped code. Is this true?
Yes, this is true. The amd_flash driver was written by me totally separate from the mtd effort. David was interested in merging it though.
/ Alex
To unsubscribe, send "unsubscribe mtd" to [email protected]