From: Blibbet <blibbet@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot roadmap?
Date: Fri, 11 Sep 2015 12:30:19 -0700 [thread overview]
Message-ID: <55F32BCB.3060505@gmail.com> (raw)
Hi,
First post on list.I'm mostly UEFI-centric, currently trying to learn
u-boot...
Is there any roadmap/plan for upcoming architectural changes to U-Boot?
I recently saw the below comment on a Debian ARM list. I'm hoping u-boot
has something like that, but more detailed, for newbies like me to
understand upcoming feature changes better. Discussion on driver models,
in particular.
On 09/11/2015 11:13 AM, Karsten Merker wrote:
> Mainline u-boot is currently in the process of slowly converting
> a large number of drivers and boards to the new driver model,
> which allows deriving platform configuration from device-trees.
> Whether and how it might be possible to adapt the kernel
> overlay model for u-boot as well is still open; work on
> u-boot in that area depends on the kernel side being settled
> first.
PS: BTW, nice to see the "U-Boot Verified Boot" feature!
Thanks,
Lee Fisher
RSS: http://firmwareescurity.com/feed
next reply other threads:[~2015-09-11 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 19:30 Blibbet [this message]
2015-09-11 23:12 ` [U-Boot] U-boot roadmap? Lukasz Majewski
2015-09-12 0:50 ` Blibbet
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=55F32BCB.3060505@gmail.com \
--to=blibbet@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.