* Re: jffs for amd Am29LV160BB
[not found] <3AE1F867.20AA5B46@sri.receiptcity.com>
@ 2001-04-21 12:05 ` David Woodhouse
0 siblings, 0 replies; 3+ messages in thread
From: David Woodhouse @ 2001-04-21 12:05 UTC (permalink / raw)
To: dhammika; +Cc: jffs-dev, mtd
(redirected to MTD list)
dhammika@sri.receiptcity.com said:
> i'm working on a StrongArm based device with two 4Mb amd Am29LV160BB
> flash chips. are these chips currently supported ??
They should work fine. Isn't the 29LV160 a 16Mib (== 2MiB) chip, though?
Meaning you have 4MiB of flash in total.
It's complaining that your assigned partitions extend over the end of the
device(s) found. What partition sizes had you told it?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: jffs for amd Am29LV160BB
[not found] <3AE31067.9C72314B@sri.receiptcity.com>
@ 2001-04-22 11:00 ` David Woodhouse
0 siblings, 0 replies; 3+ messages in thread
From: David Woodhouse @ 2001-04-22 11:00 UTC (permalink / raw)
To: dhammika; +Cc: jffs-dev, mtd
On Sun, 22 Apr 2001, dhammika wrote:
> >They should work fine. Isn't the 29LV160 a 16Mib (== 2MiB) chip, though?
> >Meaning you have 4MiB of flash in total.
>
> i'm not really sure that i understand you, i have 32bit bus and _two_
> 4MB 16bit chips. so that would give me total of 8MB flash.
You have said that you're using two Am29LV160 chips. As far as I can tell
from the AMD web site, they're _not_ 4MiB chips, they're 2MiB chips...
(http://www.amd.com/products/nvd/techdocs/techdocs.html)
Am29LV160D
16 Mbit (2 M x 8-Bit/1 M x 16-Bit)
See also http://www.amd.com/products/nvd/techdocs/22358.pdf
> another thing that i noticed is that 29LV160DD and 29LV160DB chips are
> listed in amd_flash.c this file would be compiled for non-cfi compliant
> AMD chips, but AMD schematic for 29LV160D.. says that they are cfi
> compliant. am i missing something here ??
Those chips can be driven either by the old pre-CFI driver (which also
lists them explicitly as 2MiB chips), or by the new CFI driver. CFI
doesn't provide a common interface for driving flash chips - only a common
interface for querying them to see what interface you _do_ need for
driving them. In all cases, manufacturers have just added the CFI
capability and then continued to use the original 'command sets'. So after
the initial probe, the code for driving CFI type 2 (AMD) chips is
basically identical to the code in the old AMD-specific chip driver. Some
time in the 2.5 timeframe, we're hoping to merge them properly.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: jffs for amd Am29LV160BB
[not found] ` <3AE9CCCB.10BC1502@sri.receiptcity.com>
@ 2001-04-27 8:10 ` David Woodhouse
0 siblings, 0 replies; 3+ messages in thread
From: David Woodhouse @ 2001-04-27 8:10 UTC (permalink / raw)
To: dhammika; +Cc: Nicolas Pitre, mtd
dpathirana@sri.receiptcity.com said:
> $Last[2] is 19851985, datum is 20031985
Looks like the command set driver isn't dealing properly with having 2
16-bit chips in parallel on a 32-bit bus. I thought other people were using
that arrangement, though.
Take a closer look at do_write_oneword() in cfi_cmdset_0002.c and at the
32-bit read function of the map driver.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-04-27 8:10 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <Pine.LNX.4.33.0104251247350.4186-100000@xanadu.home>
[not found] ` <3AE9CCCB.10BC1502@sri.receiptcity.com>
2001-04-27 8:10 ` jffs for amd Am29LV160BB David Woodhouse
[not found] <3AE31067.9C72314B@sri.receiptcity.com>
2001-04-22 11:00 ` David Woodhouse
[not found] <3AE1F867.20AA5B46@sri.receiptcity.com>
2001-04-21 12:05 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox