linux-kernel - Re: [PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 12 Dec 2017 19:40:52 +0100
From:   Ladislav Michl <ladis@...ux-mips.org>
To:     "Derald D. Woods" <woods.technical@...il.com>
Cc:     Tony Lindgren <tony@...mide.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 12:24:02PM -0600, Derald D. Woods wrote:
> On Tue, Dec 12, 2017 at 10:15:03AM -0800, Tony Lindgren wrote:
> > Well that's good to hear :) My only concern with your patch is what
> > happens if somebody boots with older u-boot with different partition
> > sizes?
> 
> I agree. The 'bootargs' mechanisms have seen some recent changes that
> may be a factor in what I am seeing. I had to include the command line
> in my config to test some NAND partitioning schemes and UBI. I am
> learning and Hopefully fixing some things as I go.

u-boot/board/isee/igep00x0/igep00x0.c is using only two MTD partitions,
runtime generated. As OMAP's BootROM tries to read from atmost first
four sectors before it gives up, size of SPL partiton is runtime
generated according to NAND sector size. The rest of NAND is UBI managed.
This of course breaks backward compatibility, but is unlikely to break
in future. Someone needs to decide :)

	ladis