* MTD 16M Flash module detection error?
@ 2002-06-14 2:44 Sleepy
2002-06-14 7:35 ` David Woodhouse
0 siblings, 1 reply; 2+ messages in thread
From: Sleepy @ 2002-06-14 2:44 UTC (permalink / raw)
To: linux-mtd
I have a flash module come with Linkup7205SDB, which got total 8 AM29LV160DT
chips on it. We use it in 32bit mode 4way interleave. But some how I only
can detect the first 8M, the kernel give me the following messages:
Physmap flash device: 1000000 at 80000000
Physically mapped flash: Found 4 x16 devices at 0x0 in 32-bit mode
Amd/Fujisu Extended Query Table v1.0 at 0x0040
Physically mapped flash: JEDEC Device ID is 0xc4. Assuming broken CFI table.
Physically mapped flash: Swapping erase regions for broken CFI table.
Number of CFI chips: 1
0: offset=0x0, size=0x40000 blocks=31
1: offset=0x7c0000, size=0x20000 blocks=1
2: offset=0x7e0000, size=0x8000 blocks=2
3: offset=0x7F0000, size=0x10000 blocks=1
Creating 2 MTD partitions on "Physically mapped flash":
0x00000000 - 0x00200000 : "MYMTD0"
mtd: Giving out device 0 to MYMTD0
0x00200000 - 0x01000000 : "MYMTD1"
mtd: partition "MYMTD1" extends beyond the end of device "Physically mapped
flash" ------ size truncated to 0x600000
mtd: Giving out device 1 to MYMTD1
.
.
.
does any one know why I can not use the other 8M on the module?
thanks
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MTD 16M Flash module detection error?
2002-06-14 2:44 MTD 16M Flash module detection error? Sleepy
@ 2002-06-14 7:35 ` David Woodhouse
0 siblings, 0 replies; 2+ messages in thread
From: David Woodhouse @ 2002-06-14 7:35 UTC (permalink / raw)
To: Sleepy; +Cc: linux-mtd
sleepygod@sina.com said:
> I have a flash module come with Linkup7205SDB, which got total 8
> AM29LV160DT chips on it. We use it in 32bit mode 4way interleave. But
> some how I only can detect the first 8M, the kernel give me the
> following messages:
> Physmap flash device: 1000000 at 80000000
> Physically mapped flash: Found 4 x16 devices at 0x0 in 32-bit mode A
OK... can you try configuring the Physmap device to probe only for the
_second_ set of flash chips -- are they at 0x80800000?
If it finds them there, we need to add some debugging code and work out why
it's not doing so after finding the first set.
--
dwmw2
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-06-14 7:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-14 2:44 MTD 16M Flash module detection error? Sleepy
2002-06-14 7:35 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox