speaking of linux 2.6 on the meshcube: the last major problem i have with 2.6
support is MTD: the flash size is not recognized correctly.
+#define BOARD_MAP_NAME "MTX-1 Flash"
+#define BOARD_FLASH_SIZE 0x02000000 /* 32MB */
+#define BOARD_FLASH_WIDTH 4 /* 32-bits */
to drivers/mtd/maps/alchemy-flash.c, which is about the aequivalent of what
was necessary for the 2.4 kernel.
but now flash is not recognized correctly anymore, it seems only half of it is
recognized. here is the output (with some debugging printk's from me):
MTX-1 Flash: probing 32-bit flash bus
*** map_info size: 2000000
MTX-1 Flash: Found 1 x32 devices at 0x0 in 32-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
Using buffer write method
MTX-1 Flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
*** mtd_info size: 1000000
Creating 4 MTD partitions on "MTX-1 Flash":
0x00000000-0x01c00000 : "User FS"
mtd: partition "User FS" extends beyond the end of device "MTX-1 Flash" --
size truncated to 0x1000000
mtd: Giving out device 0 to User FS
0x01c00000-0x01d00000 : "YAMON"
mtd: partition "YAMON" is out of reach -- disabled
mtd: Giving out device 1 to YAMON
0x01d00000-0x01fc0000 : "raw kernel"
mtd: partition "raw kernel" is out of reach -- disabled
mtd: Giving out device 2 to raw kernel
0x01fc0000-0x02000000 : "YAMON env"
mtd: partition "YAMON env" is out of reach -- disabled
mtd: Giving out device 3 to YAMON env
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
since we have two AMDL128ML flash chips (which are 16bit) on board, i also
tried it with BOARD_FLASH_WIDTH 2, but this leads to the same errors.
does the alchemy-flash mapping work for the other au1xxx users? any ideas what
might be the problem?
thanks for any hints,
Description: PGP signature