From: Chuck Meade <chuckmeade@gmail.com>
To: u-boot@lists.denx.de
Subject: Can U-Boot create mtdparts from device tree partition info?
Date: Wed, 6 Mar 2024 11:48:39 -0500 [thread overview]
Message-ID: <29244d1c-ec74-4d98-8137-aefabf4fe253@gmail.com> (raw)
Hello,
In looking through the source, I'm not yet seeing logic that allows U-Boot to actually use MTD partition information found in the device tree. Does this logic exist and I'm just missing it? Or do I
need to parse the device tree partitions manually and create the mtdparts env variable?
Sorry if this is obvious, I'm just not seeing it yet. Also, if the answer is just to manually enter the mtdparts env variable, and keep it in line with the partition information in the device tree as
a manual operation, please let me know that too. I'm just hoping there is a way to have U-Boot get the info from the device tree automatically.
Thanks very much,
Chuck
next reply other threads:[~2024-03-06 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 16:48 Chuck Meade [this message]
2024-03-07 9:17 ` Can U-Boot create mtdparts from device tree partition info? Alexander Dahl
2024-03-07 22:10 ` Chuck Meade
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=29244d1c-ec74-4d98-8137-aefabf4fe253@gmail.com \
--to=chuckmeade@gmail.com \
--cc=u-boot@lists.denx.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