From: Ladislav Michl <ladis@linux-mips.org>
To: "Derald D. Woods" <woods.technical@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information
Date: Tue, 12 Dec 2017 19:40:52 +0100 [thread overview]
Message-ID: <20171212184052.GA11423@lenoch> (raw)
In-Reply-To: <20171212182401.GB7404@DeraldWoods-PC.wicab.com>
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
next prev parent reply other threads:[~2017-12-12 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 4:12 [PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information Derald D. Woods
2017-12-12 6:39 ` Ladislav Michl
2017-12-12 16:31 ` Derald D. Woods
2017-12-12 16:55 ` Tony Lindgren
2017-12-12 17:50 ` Ladislav Michl
2017-12-12 18:08 ` Derald D. Woods
2017-12-12 18:15 ` Tony Lindgren
2017-12-12 18:24 ` Derald D. Woods
2017-12-12 18:40 ` Ladislav Michl [this message]
[not found] ` <CAHCN7xKn2-6NVhy6MegJgEZrF3=DFigvHW6xf0Gb2BFRTJMDNw@mail.gmail.com>
2017-12-13 13:44 ` Derald D. Woods
2017-12-13 15:05 ` Ladislav Michl
2017-12-13 15:37 ` Derald D. Woods
2017-12-12 17:03 ` Ladislav Michl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171212184052.GA11423@lenoch \
--to=ladis@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=woods.technical@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).