From: "Derald D. Woods" <woods.technical@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Ladislav Michl <ladis@linux-mips.org>,
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 12:24:02 -0600 [thread overview]
Message-ID: <20171212182401.GB7404@DeraldWoods-PC.wicab.com> (raw)
In-Reply-To: <20171212181503.GE14441@atomide.com>
On Tue, Dec 12, 2017 at 10:15:03AM -0800, Tony Lindgren wrote:
> * Derald D. Woods <woods.technical@gmail.com> [171212 18:11]:
> > On Tue, Dec 12, 2017 at 06:50:54PM +0100, Ladislav Michl wrote:
> > > On Tue, Dec 12, 2017 at 08:55:42AM -0800, Tony Lindgren wrote:
> > > > * Derald D. Woods <woods.technical@gmail.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 :)
> >
> > I am aware of all of these things. From an architectural standpoint I
> > agree with everything that has been said. But has anyone checked booting
> > lately? I helped fix an issue in U-Boot, a few months ago, where
> > OMAP34XX boards could not boot for one and half releases. Structural
> > changes were introduced, but booting was not verified on older OMAP3
> > boards. I will build with clean configs, for both U-Boot and Linux, and
> > report my findings on this thread. I recently took over maintaining the
> > OMAP3-EVM in U-Boot. This is why I am pursuing this effort. I am just
> > looking for the consistent and bootable method going forward. It will be
> > later tonight before I can verify builds.
>
> 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.
- Derald
next prev parent reply other threads:[~2017-12-12 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 4:12 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 [this message]
2017-12-12 18:40 ` Ladislav Michl
[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=20171212182401.GB7404@DeraldWoods-PC.wicab.com \
--to=woods.technical@gmail.com \
--cc=ladis@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®