From: marvin24@gmx.de (Marc Dietrich)
To: linux-arm-kernel@lists.infradead.org
Subject: Multi-platform, and secure-only ARM errata workarounds
Date: Tue, 26 Feb 2013 10:36:09 +0100 [thread overview]
Message-ID: <4928288.ie8EUukfVD@fb07-iapwap2.physik.uni-giessen.de> (raw)
In-Reply-To: <512BF81A.3080700@wwwdotorg.org>
Stephen,
Am Montag, 25. Februar 2013, 16:47:38 schrieb Stephen Warren:
> I'm looking into enabling CONFIG_MULTIPLATFORM on Tegra for 3.10, and
> the main blocking issue is due to commit 62e4d35 "ARM: 7609/1: disable
> errata work-arounds which access secure registers". Various Tegra
> versions need 3 of those workarounds, and our bootloader doesn't
> implement them (at the least, upstream U-Boot; not sure about our
> downstream code, but I'm fairly sure given the lack of any feedback I
> got in the bug I filed to implement them).
>
> 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.
> Is there any other alternative I'm not seeing? Having the kernel
> suddenly become incompatible with any currently extant bootloader when I
> enable CONFIG_MULTIPLATFORM doesn't seem like a great idea.
I *think* it's ok to deprecate fastboot on older devices. AFAIK, the in-kernel
supported boards all have u-boot support already.
Marc
next prev parent reply other threads:[~2013-02-26 9:36 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 [this message]
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
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=4928288.ie8EUukfVD@fb07-iapwap2.physik.uni-giessen.de \
--to=marvin24@gmx.de \
--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).