From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] v2016.05-rc3
Date: Wed, 27 Apr 2016 11:04:19 -0400 [thread overview]
Message-ID: <20160427150419.GF29322@bill-the-cat> (raw)
In-Reply-To: <8760v442cp.fsf@aikidev.net>
On Tue, Apr 26, 2016 at 12:05:58PM -0700, Vagrant Cascadian wrote:
> On 2016-04-25, Tom Rini wrote:
> > I know I did v2016.05-rc2 just last week, but that's because I was off
> > schedule. We are two weeks out from scheduled release, so he's -rc3.
> > Please test this everywhere you can.
>
> I'm having issues with v2016.05-rc3 booting beaglebone black from eMMC
> and microSD, reverting ef5ebe951bec72631cdbc7cef9079e6c684e5d0b
> "ti_armv7_common.h: Fix U-Boot location on eMMC" seems to fix the issue
> for me.
>
> It appears this patch changed where the raw offsets for loading
> u-boot.img are, though the "old" offsets are already in widespread use,
> so would be unfortunate to have to change them everywhere else.
Indeed this is a problem. I think for this release we might have to
revert the change and then moving forward extend SPL to allow this
location to come via the environment (which we do for example with
bootcount) so that other use-cases can change things as needed. Sorry
for the confusion, I had thought the patch was doing something slightly
different than it is.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160427/df513eb5/attachment.sig>
prev parent reply other threads:[~2016-04-27 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 0:18 [U-Boot] [ANN] v2016.05-rc3 Tom Rini
2016-04-26 18:33 ` Wolfgang Denk
2016-04-26 19:05 ` Vagrant Cascadian
2016-04-27 15:04 ` Tom Rini [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=20160427150419.GF29322@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