[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash



On Wed, Jun 26, 2013 at 01:13:58 +0100, Ben Hutchings wrote:
> My reading of the m25p_probe() function is that if the named chip has a
> JEDEC ID, and the chip it finds has a different JEDEC ID that's also in
> the device ID table, it will then automatically adapt (but will warn).
> 
> So long as the same partition map is used for the two chips, I think the
> platform code should just probe once as now, though the warning is
> annoying.  It seems like there ought to be a way to tell m25p80 to
> auto-detect and warn only if the size doesn't match the partition map.

FWIW, I successfully installed on this QNAP using a daily installer [1]
running 3.9-1-kirkwood. Here is the dmesg snippet probing the flash,
looks exactly like what you describe:

[    8.328203] m25p80 spi0.0: found n25q128a13, expected m25p128
[    8.334003] m25p80 spi0.0: n25q128a13 (16384 Kbytes)
[    8.338989] Creating 6 MTD partitions on "spi_flash":
[    8.344074] 0x000000000000-0x000000080000 : "U-Boot"
[    8.349708] 0x000000200000-0x000000400000 : "Kernel"
[    8.355309] 0x000000400000-0x000000d00000 : "RootFS1"
[    8.360987] 0x000000d00000-0x000001000000 : "RootFS2"
[    8.366689] 0x000000080000-0x0000000c0000 : "U-Boot Config"
[    8.372895] 0x0000000c0000-0x000000200000 : "NAS Config"

[1] http://d-i.debian.org/daily-images/armel/20130625-08:44/kirkwood/network-console/qnap/ts-219/

-- 
mike


Reply to: