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
| ||
|
Message-ID: <20171212175054.GA10337@lenoch> Date: Tue, 12 Dec 2017 18:50:54 +0100 From: Ladislav Michl <ladis@...ux-mips.org> To: Tony Lindgren <tony@...mide.com> Cc: "Derald D. Woods" <woods.technical@...il.com>, linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information On Tue, Dec 12, 2017 at 08:55:42AM -0800, Tony Lindgren wrote: > * Derald D. Woods <woods.technical@...il.com> [171212 16:34]: > > I am testing using an appended device-tree. This has been the most > > reliable method for the OMAP34XX boards that I have. If you have an > > example config, with working command line MTDPARTS, for beagleboard(Rev. > > C4), Overo TOBI, or similiar OMAP34XX, I will gladly use it. Also note > > that other OMAP34XX boards currently provide a default partition > > layout. Is that bad practice for all of those as well? I am open to > > exploring the method that actually works. > > I think we came to the conclusion at some point that it's best to rely > on u-boot passed partitions because with later u-boot versions the > size was increased for the bootloader partition. > > Ideally of course we would read the partition information from the > MTD device somewhere.. Already done and called UBI :)
Powered by blists - more mailing lists