From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot as first bootloader on Exynos platforms
Date: Fri, 04 Mar 2016 08:12:06 +0100 [thread overview]
Message-ID: <1457075526.1386.0.camel@paulk.fr> (raw)
In-Reply-To: <CAPnjgZ0Pxdt1pizQGsqFMaToEd4MF3FpcK8gGHR-er-1MoBs-A@mail.gmail.com>
Hi,
Le mardi 01 mars 2016 ? 06:27 -0700, Simon Glass a ?crit?:
> On 1 March 2016 at 01:10, Paul Kocialkowski <contact@paulk.fr> wrote:
> > Hi,
> > Le lundi 29 f?vrier 2016 ? 19:03 -0700, Simon Glass a ?crit :
> > > On 29 February 2016 at 03:15, Lukasz Majewski <l.majewski@samsung.com>
> > > wrote:
> > > > > I was told some time ago that a publicly-available version of the
> > > > > Samsung Chromebook 2 (supposedly, the one with an Exynos 5800 SoC)
> > > > > allows running unsigned code (the U-Boot SPL) directly after the
> > > > > bootrom. Is that correct?
> > > > >
> > > > > Do you know of any (other) publicly available device with an Exynos
> > > > > SoC that doesn't check for the first bootloader's signature, and thus
> > > > > could load the U- Boot SPL without any intermediary signed stage on
> > > > > storage memory?
> > > >
> > > > For sure Odroid XU3 needs signed SPL to boot up, so this devel board
> > > > will not work for you.
> > >
> > > You can use snow which is Chromebook 1, or pit / pi which are
> > > Chromebook 2. I have not tried its 'BL1' with Odroid XU3 but I doubt
> > > it will work.
> >
> > I know those have U-Boot support, but do any of them work without the
> > proprietary and signed on-memory first stage bootloaders?
> >
> > I was told that at least snow's bootrom checks the signature of the first
> > bootloader it loads from memory. Is it the case for all Exynos devices?
>
> I think that is true for all. But in the case of these Chromebooks,
> the BL1 does not check the signature of the image it loads, which
> breaks the chain. For Chrome OS, this kind of restriction is not
> useful, since the user should be able to run their own software on the
> platform. I'm really not sure why XU3 cannot do this too.
Thanks for the clarification!
--
Paul Kocialkowski, low-level free software developer on embedded devices
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160304/b3d5d071/attachment.sig>
prev parent reply other threads:[~2016-03-04 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 13:41 [U-Boot] U-Boot as first bootloader on Exynos platforms Paul Kocialkowski
2016-02-29 10:15 ` Lukasz Majewski
2016-03-01 2:03 ` Simon Glass
2016-03-01 8:10 ` Paul Kocialkowski
2016-03-01 13:27 ` Simon Glass
2016-03-04 7:12 ` Paul Kocialkowski [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=1457075526.1386.0.camel@paulk.fr \
--to=contact@paulk.fr \
--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