Re: AM29DL16x series driver

Re: AM29DL16x series driver

[Marco A. Moreno]

--- Alexander Larsson <alex@cendio.se> wrote:
> 
> 
> On Fri, 15 Oct 1999, Marco A. Moreno wrote:
> 
> > Hi,
> > 
> > I'm working on a project that is slated to use the 'DL162 and 'DL163 AMD
> parts.
> > I saw in the archives that someone wrote an 'LV160 driver.  I want to know
> if
> > there would be significant changes to the driver to support the DL parts
> which
> > 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 majordomo@imladris.demon.co.uk

Re: AM29DL16x series driver

[Alexander Larsson]

On Fri, 15 Oct 1999, Marco A. Moreno wrote:
> --- Alexander Larsson <alex@cendio.se> wrote:
> > 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?

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 majordomo@imladris.demon.co.uk

AM29DL16x series driver

[Marco A. Moreno]

Hi,

I'm working on a project that is slated to use the 'DL162 and 'DL163 AMD parts.
 I saw in the archives that someone wrote an 'LV160 driver.  I want to know if
there would be significant changes to the driver to support the DL parts which
differ in that they have flexible sectors.  Does the CFI take care of this? 
Any info would be greatly appreciated.

Thanks,
Marco


=====

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


To unsubscribe, send "unsubscribe mtd" to majordomo@imladris.demon.co.uk

Re: AM29DL16x series driver

[Alexander Larsson]

On Fri, 15 Oct 1999, Marco A. Moreno wrote:

> Hi,
> 
> I'm working on a project that is slated to use the 'DL162 and 'DL163 AMD parts.
> I saw in the archives that someone wrote an 'LV160 driver.  I want to know if
> there would be significant changes to the driver to support the DL parts which
> 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



To unsubscribe, send "unsubscribe mtd" to majordomo@imladris.demon.co.uk

Re: AM29DL16x series driver

[D. Jeff Dionne / VE3DJF]

> Hi,
> 
> I'm working on a project that is slated to use the 'DL162 and 'DL163 AMD parts.
>  I saw in the archives that someone wrote an 'LV160 driver.  I want to know if

If the driver uses CFI, the problem is going to be that (some of?) the DL
series parts don't support CFI.  The Am29DL800 does not, for instance.
I'm not sure, but perhaps the reason is that CFI does not have the
concept of a split map with concurrent read/write capibility.  This
is a major issue for uClinux hardware, since we can't always be sure of a 
supply of LV _or_ DL parts.  Have you tried to buy these yet?  Good luck,
it's sort of take what you can get or wait.  It's not a harware problem
though, all are pin compatible from LV400 up to DL323.  The software
interface is not the same, so we can't rely on _any_ feature one series
has that the other does not if we want to keep our options open.

The only common functionality we feel we can be sure of is the Mfg and 
Type ID to find the sector sizes from a table.  Then we use the smallest
subset of commands common to all types we might end up using.


D. Jeff Dionne.

> there would be significant changes to the driver to support the DL parts which
> differ in that they have flexible sectors.  Does the CFI take care of this? 
> Any info would be greatly appreciated.
> 
> Thanks,
> Marco
> 
> 
> =====
> 
> __________________________________________________
> Do You Yahoo!?
> Bid and sell for free at http://auctions.yahoo.com
> 
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo@imladris.demon.co.uk
> 



To unsubscribe, send "unsubscribe mtd" to majordomo@imladris.demon.co.uk