From: gianluca <gianlucarenzi@eurekelettronica.it>
To: barebox@lists.infradead.org
Subject: Re: Kernel device tree gets modified with bootm command when CONFIG_OFDEVICE is enabled
Date: Fri, 6 Oct 2017 13:04:36 +0200 [thread overview]
Message-ID: <724ccd1e-493c-b6dd-e0aa-ea65828fb6bf@eurekelettronica.it> (raw)
In-Reply-To: <0ad15ca1-bad1-a631-89fa-53ddc4ba224e@solidxs.nl>
On 10/06/2017 12:28 PM, Marcel Hamer wrote:
> Hello Ian,
>
>> 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").)
>>
>
> Thank you for pointing that option out, I will certainly have a look at
> that.
>
> I took the partitioning as an example, because it gave me the biggest
> burden. But I guess in general I think the principle of fixing up the
> kernel device tree should be optional to my opinion.
>
IMHO you Marcel, are missing the point.
Do not changing device tree and passing it as-is to the kernel has the
reason on systems non upgradable, non changeable during their life-time.
i.e. routers and or smartphones.
Usually they are provided with all stuff attached and normally everyting
is working out-of-the-box.
To my experience, we have a bunch of boards, and they are different each
other by little stuff, such as number of uarts, gpios, screens/lcd,
memory and storage size.
I am letting BareBox to adapt a "generic-all-inclusive" device-tree with
the correct "device-tree" to the kernel, so it can be used without
hassle having and managing a single device-tree in our develpement studio.
It is simpler to have a single device-tree which can be used over a
plethora of boards based on the same root-hardware, than having a
plethora of device-trees perfectly adapted with your plethora of devices.
Do you agree?
Regards,
Gianluca
--
Eurek s.r.l. |
Electronic Engineering | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-10-06 11:05 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
2017-10-06 10:28 ` Marcel Hamer
2017-10-06 11:04 ` gianluca [this message]
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=724ccd1e-493c-b6dd-e0aa-ea65828fb6bf@eurekelettronica.it \
--to=gianlucarenzi@eurekelettronica.it \
--cc=barebox@lists.infradead.org \
/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