From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Andreas_Bie=DFmann?= <andreas.devel@googlemail.com>
Date: Tue, 02 Jul 2013 12:37:30 +0200
Subject: [U-Boot] [ANN] v2013.07-rc2
In-Reply-To: <CAOCHtYjD-v+XisPkDc2n9Rth73LqEuoB9070gBAKwcmxYQ-fLw@mail.gmail.com>
References: <20130628221222.GM28078@bill-the-cat>
	<CAOCHtYjD-v+XisPkDc2n9Rth73LqEuoB9070gBAKwcmxYQ-fLw@mail.gmail.com>
Message-ID: <51D2AD6A.1030708@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi,

On 07/01/2013 10:44 PM, Robert Nelson wrote:
> On Fri, Jun 28, 2013 at 5:12 PM, Tom Rini <trini@ti.com> wrote:
>> Hey all,
>>
>> I've tagged and pushed v2013.07-rc2.  A bit more over the place than I
>> should have gone, but picked up a lot of things that have been
>> outstanding for a while.  The big thing is a refactor of the boot loop.
>> Everything should be working right now, but please test.  Related to
>> this is the ability to have crytpographically signed images.  It's like
>> secure boot in UEFI land, but hopefully without the kerfuffle.
>>
>> If you've got changes outstanding still, please start gently poking
>> custodians with patchwork links.  I've got a good bit of stuff I need to
>> deal with myself still, but please prod me all the same.
> 
> So, the bootm refactor ( 35fc84fa1ff51e15ecd3e464dac87eb105ffed30 )
> also broke bootz/zImage...

and also bootm for uImage on avr32 ... will investigate it these days.

Best regards

Andreas Bie?mann