From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from usti.fccps.cz ([194.108.74.250]) by canuck.infradead.org with esmtp (Exim 4.42 #1 (Red Hat Linux)) id 1CjeTO-0007zq-8H for linux-mtd@lists.infradead.org; Wed, 29 Dec 2004 09:06:47 -0500 Received: from localhost (localhost [127.0.0.1]) by usti.fccps.cz (Postfix) with ESMTP id 77D3577C89 for ; Wed, 29 Dec 2004 15:06:40 +0100 (CET) Received: from usti.fccps.cz ([127.0.0.1]) by localhost (usti [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23074-04 for ; Wed, 29 Dec 2004 15:06:39 +0100 (CET) Received: from frr (unknown [10.0.0.238]) by usti.fccps.cz (Postfix) with ESMTP id EB4E677C85 for ; Wed, 29 Dec 2004 15:06:38 +0100 (CET) From: "Frantisek Rysanek" To: linux-mtd@lists.infradead.org Date: Wed, 29 Dec 2004 15:10:27 +0100 MIME-Version: 1.0 Content-type: Multipart/Mixed; boundary=Message-Boundary-4951 Message-ID: <41D2C8E3.26470.C13D47B@localhost> Subject: several bugfixes/workarounds in mtd snapshot of 20041226 && 2.4.28 List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --Message-Boundary-4951 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Dear MTD maintainers, I suggest several bugfixes and workarounds against the snapshot of 20041226 (inserted into a vanilla 2.4.28) - see the attached patch. I'm using DiskOnChip devices in various sorts of Advantech hardware. I'm compiling my MTD drivers for the DiskOnChip alone - I don't want to include all the other MTD stuff (useless to me). Bugs fixed / worked around: 1) if you flush the partition table and issue a BLKRRPART (i.e., you re-partition the diskonchip), the reported device size shrinks to one half of the original. If you do this again before a reboot, the size shrinks again (now one quarter). Seems like the driver would re-init device size to a size denominated in 1k blocks, rather than sectors (512B). 2) in my DiskOnChip-only setup, CONFIG_MTD_MAP_BANK_WIDTH_1 is missing in the .config. I've added that straight to $LINUX/include/linux/map.h 3) two #includes seem to be missing in $MTD/nand/diskonchip.c 4) the Reed-Solomon library hooks are messed up in $LINUX/lib/Config.in I hope this helps Frank Rysanek --Message-Boundary-4951 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Text from file 'mtd-bugs.20041226.patch' --- linux_with_mtd_bugs/drivers/mtd/mtd_blkdevs-24.c 2004-12-27 14:48:52.000000000 +0100 +++ linux/drivers/mtd/mtd_blkdevs-24.c 2004-12-29 14:32:14.000000000 +0100 @@ -315,7 +315,7 @@ } grok_partitions(gd, minor, 1 << tr->part_bits, - tr->blkcore_priv->sizes[minor]); + dev->size); up(&mtd_table_mutex); return 0; --- linux_with_mtd_bugs/include/linux/mtd/map.h 2004-12-27 14:48:54.000000000 +0100 +++ linux/include/linux/mtd/map.h 2004-12-27 15:33:58.000000000 +0100 @@ -14,6 +14,10 @@ #include #include +#ifndef CONFIG_MTD_CFI_GEOMETRY +#define CONFIG_MTD_MAP_BANK_WIDTH_1 +#endif + #ifdef CONFIG_MTD_MAP_BANK_WIDTH_1 #define map_bankwidth(map) 1 #define map_bankwidth_is_1(map) (map_bankwidth(map) == 1) --- linux_with_mtd_bugs/drivers/mtd/nand/diskonchip.c 2004-12-27 14:48:53.000000000 +0100 +++ linux/drivers/mtd/nand/diskonchip.c 2004-12-27 13:39:56.000000000 +0100 @@ -24,6 +24,8 @@ #include #include #include +#include +#include #include #include --- linux_with_mtd_bugs/lib/Config.in 2004-12-27 14:48:54.000000000 +0100 +++ linux/lib/Config.in 2004-12-29 14:37:35.000000000 +0100 @@ -43,13 +43,15 @@ if [ "$CONFIG_MTD_DOCPROBE" = "y" -o \ "$CONFIG_MTD_NAND_RTC_FROM4" = "y" -o \ - "$MTD_NAND_DISKONCHIP" = "y" ]; then + "$CONFIG_MTD_NAND_DISKONCHIP" = "y" ]; then define_tristate CONFIG_REED_SOLOMON y + define_tristate CONFIG_REED_SOLOMON_DEC16 y else if [ "$CONFIG_MTD_DOCPROBE" = "m" -o \ "$CONFIG_MTD_NAND_RTC_FROM4" = "m" -o \ - "$MTD_NAND_DISKONCHIP" = "m" ]; then + "$CONFIG_MTD_NAND_DISKONCHIP" = "m" ]; then define_tristate CONFIG_REED_SOLOMON m + define_tristate CONFIG_REED_SOLOMON_DEC16 y else define_tristate CONFIG_REED_SOLOMON n fi --Message-Boundary-4951--