From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v9 0/2] Basic Kontron SMARC-sAL28 board support
Date: Tue, 27 Oct 2020 18:27:54 -0400 [thread overview]
Message-ID: <20201027222754.GD5340@bill-the-cat> (raw)
In-Reply-To: <9a87863c620cc63288102dbfd8b180b2@walle.cc>
On Tue, Oct 27, 2020 at 11:23:23PM +0100, Michael Walle wrote:
> Hi Tom, Hi all,
>
> Am 2020-10-15 23:08, schrieb Michael Walle:
> > Add basic board support for the Kontron SMARC-sAL28 board. Please note,
> > that this board doesn't support TF-a (yet). Therefore, the u-boot SPL is
> > the first code which is run and it has to set up the RAM.
>
> With the merge window closing.. seems like this patch series will also
> miss this release. TBH this is really frustrating.
> The first version was posted on May this year. Most versions were just
> follow-ups by me because missing features used by this boards were
> already merged into u-boot and thus I've updated this patch series
> accordingly to use the new feature.
I would really expect "just add a board" to be merged up until maybe
-rc3 or -rc4 is out, honestly.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201027/b46f41f6/attachment.sig>
next prev parent reply other threads:[~2020-10-27 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 21:08 [PATCH v9 0/2] Basic Kontron SMARC-sAL28 board support Michael Walle
2020-10-15 21:08 ` [PATCH v9 1/2] board: kontron: add sl28 support Michael Walle
2020-10-15 21:08 ` [PATCH v9 2/2] board: sl28: add board specific nvm command Michael Walle
2020-10-27 22:23 ` [PATCH v9 0/2] Basic Kontron SMARC-sAL28 board support Michael Walle
2020-10-27 22:27 ` Tom Rini [this message]
2020-10-28 11:01 ` Priyanka Jain
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=20201027222754.GD5340@bill-the-cat \
--to=trini@konsulko.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