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: Mon, 16 Dec 2013 11:06:51 +0800 From: Huang Shijie <b32955@...escale.com> To: Caizhiyong <caizhiyong@...ilicon.com> CC: Huang Shijie <shijie8@...il.com>, Brian Norris <computersforpeace@...il.com>, David Woodhouse <David.Woodhouse@...el.com>, Quyaxin <quyaxin@...ilicon.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>, Artem Bityutskiy <artem.bityutskiy@...ux.intel.com>, "Wanglin (Albert)" <albert.wanglin@...ilicon.com>, David Woodhouse <dwmw2@...radead.org> Subject: Re: [PATCH] mtd: increase max page/OOB size to support 16K pagesize NAND On Mon, Dec 16, 2013 at 02:03:54AM +0000, Caizhiyong wrote: > > > > > > There are a lot of 16K page size NAND, they are used in android system. > > > > > > Many NAND need read retry and data randomization, kernel does not support this > > feature. > > Brian is adding the read-retry feature. > > > > I think the data randomization should be done by the hardware. > > If we do it by software, it costs lot of the cpu cycles. > > > > > > > Kernel also does not support synchronous NAND. > > > > The synchronous NAND should be supported by the nand controller driver, > > not the kernel. > > Yes. Those feature should be support by NAND controller hardware and driver. > But the driver does not know what NAND should use those feature. > Perhaps, the NAND id table, should add something. We can get the synchronous info from the ONFI nand. In actually, if you do not add this patch, i will change it too. I have several 16K nand chips on my hands now. :) thanks Huang Shijie -- 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