From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2018.03-rc2 released
Date: Tue, 13 Feb 2018 10:24:55 +0100 [thread overview]
Message-ID: <20180213102455.22e152c9@jawa> (raw)
In-Reply-To: <20180212235406.GN10592@bill-the-cat>
On Mon, 12 Feb 2018 18:54:06 -0500
Tom Rini <trini@konsulko.com> wrote:
> Hey all,
>
> It's release day and v2018.03-rc2 is out. The big thing is that
> there's some env related changes that need to be first sorted out and
> tested, then pulled in.
>
> Other than the env fixes, I hope to pull in some more Kconfig
> migrations. These I hope will be size neutral, but I know that a few
> things aren't due to fixing underlying omissions.
>
> Things look on track f26th, -rc4 on March 5th and then release on
> March 12th. Thanks all!
>
The patch: d695d6627803dbb78a226e04b0436a01633a9936
spl: eMMC/SD: Provide one __weak spl_boot_mode() function
Has shown some issues with fallback boot on iMX boards (which use eMMC
raw boot, even with SPL_EXT_SUPPORT defined).
I'm looing for a proper solution - but hadn't find one yet.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180213/92a03173/attachment.sig>
prev parent reply other threads:[~2018-02-13 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 23:54 [U-Boot] [ANN] U-Boot v2018.03-rc2 released Tom Rini
2018-02-13 6:04 ` Heiko Schocher
2018-02-13 9:24 ` Lukasz Majewski [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=20180213102455.22e152c9@jawa \
--to=lukma@denx.de \
--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