From: Ladislav Michl <ladis@linux-mips.org>
To: "Derald D. Woods" <woods.technical@gmail.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information
Date: Tue, 12 Dec 2017 18:03:02 +0100 [thread overview]
Message-ID: <20171212170302.GA8381@lenoch> (raw)
In-Reply-To: <20171212163125.GA8032@DeraldWoods-PC.wicab.com>
On Tue, Dec 12, 2017 at 10:31:26AM -0600, Derald D. Woods wrote:
> > What about passing U-Boot partitions information to kernel instead?
>
> 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.
Well, appended device tree is indeed good only for testing purposes
where bootloader is unable to provide one.
Problem with hardcoded partitions is that you need to keep bootloader
and kernel view of partitions the same. That's why U-Boot introduced
CONFIG_FDT_FIXUP_PARTITIONS which will add mtdparts into DTB.
ladis
prev parent reply other threads:[~2017-12-12 17:03 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
[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 [this message]
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=20171212170302.GA8381@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).