| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 7 Sep 2010 14:37:41 +0800 From: Tony Wan <visual2me@...il.com> To: linux-kernel@...r.kernel.org Subject: Fwd: anyone can help me about nand_get_flash_type Anyone can help me with this problem? even some ideas how to debug and find the problem? Thank you! ---------- Forwarded message ---------- From: Tony Wan <visual2me@...il.com> Date: Wed, Aug 25, 2010 at 5:36 PM Subject: anyone can help me about nand_get_flash_type To: linux-mtd@...ts.infradead.org Hi there, I got an ARM device from Marvell with a NAND rom, running Linux 2.6.22.18. These days I'm working on upgrading the kernel to 2.6.31.8. After the upgrade, all devices work well except the NAND rom. I found it's because that the device and manufacturer IDs cannot be retrieved correctly in nand_get_flash_type. In 2.6.22.18, the IDs can be retrieved as expected; but in 2.6.31.8, the IDs always be 0, which leads to an error in nand_scan. I'm a definitely newbie with MTD, and currently have no idea about the problem. Except IO_ADDR_R & IO_ADDR_W are remapped to different addresses, I can't find any differences between the 2 versions from the system log -- may it be the reason? Anyone can give me some tips about this problem -- how to fix it or how to debug? Any suggestions will be appreciated. -- Best regards, Tony Wan -- Best regards, Tony Wan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists