From: Ian Abbott <abbotti@mev.co.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: v2019.05.0
Date: Mon, 13 May 2019 14:21:08 +0100 [thread overview]
Message-ID: <0f7ecd36-37f5-a2cb-42e7-4d235f59db60@mev.co.uk> (raw)
In-Reply-To: <20190513122319.xg2ykm6rmipsfhlo@pengutronix.de>
On 13/05/2019 13:23, Sascha Hauer wrote:
> On Mon, May 13, 2019 at 12:27:32PM +0100, Ian Abbott wrote:
>> On 10/05/2019 08:07, Sascha Hauer wrote:
>>> Hi All,
>>>
>>> v2019.05.0 is out. This time we gained initial Layerscape support (for
>>> the LS1046a) and initial very basic STM32MP1 support. What I like best
>>> for this release is the improved pstore support. With pstore it's
>>> possible to access the last kernel log, possibly including oopses and
>>> panics. Also the barebox log is accessible from the running kernel.
>>> pstore has been present before, but with this release we got the device
>>> tree bindings, so now it's only a matter of putting the right thing
>>> into the device tree to use pstore. Give it a try, it's nice ;)
>>>
>>> Sascha
>>
>> Hi Sascha,
>>
>> The official tarball seems to be missing from the download page. Thanks.
>
> Oops, indeed. Should be there now.
Thanks!
--
-=( Ian Abbott <abbotti@mev.co.uk> || Web: www.mev.co.uk )=-
-=( MEV Ltd. is a company registered in England & Wales. )=-
-=( Registered number: 02862268. Registered address: )=-
-=( 15 West Park Road, Bramhall, STOCKPORT, SK7 3JZ, UK. )=-
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-05-13 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 7:07 v2019.05.0 Sascha Hauer
2019-05-13 11:27 ` v2019.05.0 Ian Abbott
2019-05-13 12:23 ` v2019.05.0 Sascha Hauer
2019-05-13 13:21 ` Ian Abbott [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=0f7ecd36-37f5-a2cb-42e7-4d235f59db60@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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