From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: Multi-platform, and secure-only ARM errata workarounds
Date: Wed, 27 Feb 2013 08:00:08 -0600 [thread overview]
Message-ID: <512E1168.4080003@gmail.com> (raw)
In-Reply-To: <22709540.96uJddbx1U@fb07-iapwap2.physik.uni-giessen.de>
On 02/27/2013 03:03 AM, Marc Dietrich wrote:
> Am Dienstag, 26. Februar 2013, 09:39:15 schrieb Stephen Warren:
>> On 02/26/2013 02:36 AM, Marc Dietrich wrote:
>>> Am Montag, 25. Februar 2013, 16:47:38 schrieb Stephen Warren:
>>>> ...
>>>> Now, I can easily add those 3 errata workarounds to U-Boot, but that
>>>> will require people to reflash their bootloader. This is probably
>>>> acceptable for development/reference boards (although I'm sure people
>>>> will find it annoying) but for re-purposed production boards (such as
>>>> the Toshiba AC100 or various tablets) it will be impossible to update
>>>> the factory bootloader. Switching to upstream U-Boot would currently
>>>> lose some functionality, and significantly affect people's boot flow, so
>>>> is likely unacceptable.
>>>
>>> personally, I have no problem to require a certain u-boot version for a
>>> given kernel. From a distro point of view, you will likely update the
>>> bootloader/kernel on a distro update anyway.
>>
>> So a distro will certainly update the kernel.
>>
>> But updating a bootloader would be very unusual, I believe.
>
> mmh? Every time I update to a new distro release, the bootloader gets also
> updated - even on arm, e.g. ftp://ports.ubuntu.com/ubuntu-ports/pool/main/u/u-boot-linaro lists four version of uboot - one for each supported distro
> release. I know for closed embedded device this is different, but that's not
> our target.
There is a package of u-boot bootloaders, but they are not installed by
the OS. On ubuntu, installing a kernel only writes the boot.scr script.
There is an assumption that u-boot will go and read this. So we already
have some requirements on u-boot which would require at least a u-boot
environment update. I guess updating the environment is easier than
u-boot itself, but that probably depends on the platform.
Rob
next prev parent reply other threads:[~2013-02-27 14:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 23:47 Multi-platform, and secure-only ARM errata workarounds Stephen Warren
2013-02-26 9:36 ` Marc Dietrich
2013-02-26 16:39 ` Stephen Warren
2013-02-26 22:31 ` Nicolas Pitre
2013-02-27 9:03 ` Marc Dietrich
2013-02-27 14:00 ` Rob Herring [this message]
2013-02-27 17:42 ` Stephen Warren
2013-02-28 13:58 ` Marc Dietrich
2013-02-26 10:23 ` Arnd Bergmann
2013-02-26 10:31 ` Catalin Marinas
2013-02-26 10:35 ` Catalin Marinas
2013-02-26 10:48 ` Arnd Bergmann
2013-02-26 11:11 ` Catalin Marinas
2013-02-26 11:35 ` Russell King - ARM Linux
2013-02-26 14:07 ` Rob Herring
2013-02-26 18:01 ` Stephen Warren
2013-02-26 18:11 ` Russell King - ARM Linux
2013-02-26 18:30 ` Stephen Warren
2013-02-26 18:49 ` Russell King - ARM Linux
2013-02-27 6:07 ` Santosh Shilimkar
2013-03-01 17:37 ` Stephen Warren
2013-03-01 18:05 ` Russell King - ARM Linux
2013-03-04 6:34 ` Peter De Schrijver
2013-03-04 9:16 ` Peter De Schrijver
2013-03-04 17:08 ` Stephen Warren
2013-03-05 7:40 ` Peter De Schrijver
2013-03-05 17:00 ` Stephen Warren
2013-03-06 8:14 ` Peter De Schrijver
2013-03-06 16:18 ` Stephen Warren
2013-03-10 17:25 ` Santosh Shilimkar
2013-03-10 18:47 ` Olof Johansson
2013-03-11 16:59 ` Stephen Warren
2013-03-11 18:54 ` Jason Gunthorpe
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=512E1168.4080003@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).