From: Ian Abbott <abbotti@mev.co.uk>
To: Marcel Hamer <marcel@solidxs.nl>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Kernel device tree gets modified with bootm command when CONFIG_OFDEVICE is enabled
Date: Fri, 6 Oct 2017 10:55:11 +0100 [thread overview]
Message-ID: <4cda0e44-6ac4-8186-2453-0d55919727ef@mev.co.uk> (raw)
In-Reply-To: <4201a4ed-f5ae-2cae-e07c-1e95dbb538df@solidxs.nl>
On 06/10/17 08:45, Marcel Hamer wrote:
> It kind of sounds like the boot loader is deciding it is smarter than
> the developer and overriding the settings in the dtb before it passes it
> to the kernel. I also see it as kind of strange, when you configure a
> partition table in your dtb for the kernel and once you boot the kernel
> you get the partition table from the boot loader. Especially since I
> don't think this is documented anywhere, at least not in the bootm
> command documentation as far as I know.
There is a magic variable setting to leave the partition entries alone:
global.of_partition_binding="donttouch"
(Other meaningful values for this variable are "new" and "legacy", which
controls whether the individual partitions are placed within a
"partitions" node ("new") or not ("legacy").)
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-10-06 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 9:36 Marcel Hamer
2017-10-06 4:11 ` Sascha Hauer
2017-10-06 7:45 ` Marcel Hamer
2017-10-06 9:55 ` Ian Abbott [this message]
2017-10-06 10:28 ` Marcel Hamer
2017-10-06 11:04 ` gianluca
2017-10-06 12:00 ` Marcel Hamer
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=4cda0e44-6ac4-8186-2453-0d55919727ef@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=barebox@lists.infradead.org \
--cc=marcel@solidxs.nl \
--cc=s.hauer@pengutronix.de \
/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