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: Thu, 09 Oct 2014 18:43:37 +0200 From: Richard Weinberger <richard@....at> To: Wei Wang <wangw8210@...il.com>, linux-mtd@...ts.infradead.org CC: dedeking1@...il.com, linux-arm-msm@...r.kernel.org, open list <linux-kernel@...r.kernel.org>, Brian Norris <computersforpeace@...il.com>, David Woodhouse <dwmw2@...radead.org>, Artem Bityutskiy <dedekind1@...il.com> Subject: Re: Questions about MTD + flash file system Am 09.10.2014 18:40, schrieb Wei Wang: > Hi all, > > I have a question about the MTD device for embedded applications. As typically designers are more likely to use an eMMC or block interface-based flash devices + a block-oriented > file system for the storage system on an embedded system, what's the typical use case for the MTD + flash file system? What's the advantage of the later one against eMMC + > block-oriented file system? > > If an eMMC becomes more powerful, is there any merits that is provided by using an raw flash device + flash file system? Power cut resistance. Thanks, //richard -- 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