From: Xo Wang <xow@google.com>
To: openbmc@lists.ozlabs.org
Subject: Re: u-boot tree status update
Date: Thu, 23 Jun 2016 10:58:04 -0700 [thread overview]
Message-ID: <576C232C.5070002@google.com> (raw)
In-Reply-To: <CACPK8Xd_Ex+8Ln2tLcrfueOG1nFHH3JTG3iXm5s4jbrHkbMcLw@mail.gmail.com>
Hi,
> The names aren't the best I agree. Also, most of our configuration is
> hard coded in board headers. We want to move the platforms over to
> using u-boot's Kconfig system, as well as adding support for
> Facebook's ast2400 platforms that use a different network and flash
> configuration.
Excellent work, guys. I agree with the move to Kconfig. The #define
configuration in aspeed's code is pretty hairy and probably part of what
blocks the march to upstream.
cheers
//xo
prev parent reply other threads:[~2016-06-23 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 7:33 u-boot tree status update Joel Stanley
2016-06-23 17:58 ` Xo Wang [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=576C232C.5070002@google.com \
--to=xow@google.com \
--cc=openbmc@lists.ozlabs.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 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.