From: Sascha Hauer <s.hauer@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 00/10] HYP mode handling and RasPi 3 support
Date: Tue, 6 Feb 2018 09:52:15 +0100 [thread overview]
Message-ID: <20180206085215.ndvytxn4w32wvyw3@pengutronix.de> (raw)
In-Reply-To: <20180129163004.10512-1-l.stach@pengutronix.de>
On Mon, Jan 29, 2018 at 05:29:54PM +0100, Lucas Stach wrote:
> Hi,
>
> this series allows Barebox to be entered in HYP mode. As the HYP mode
> is a whole different world it just makes sure to install the hooks
> needed to get back into HYP and then switches to SVC mode as fast as
> it can. The kernel is then started in HYP mode by default.
>
> This is needed in order to get RasPi 3 support in place, where the
> firmware opts to hand us the CPUs in HYP mode.
>
> I've tested this series on another ARMv7 board, to make sure I didn't
> break something obvious, but I would still welcome some eyeballs on
> this code, as it touches a good deal of the lowlevel code.
>
> Enrico Joerns (1):
> ARM: rpi: add revision IDs for Pi 3 Model B and Pi Zero
>
> Lucas Stach (9):
> ARM: import opcode helpers from Linux kernel
> ARM: safely switch from HYP to SVC mode if required
> ARM: allow secure monitor code to be built without PSCI
> ARM: add file for HYP mode related setup
> ARM: don't try to install secure monitor when entered in HYP mode
> ARM: default to starting kernel in HYP mode when entered in HYP
> ARM: install HYP vectors at PBL and Barebox entry
> ARM: rpi: add raspberry pi 3 support
> ARM: rpi: autosize malloc area
I applied this series for now. Besides on the tests already done by you
I gave it a try on ARMv5 and it doesn't break anything obvious there
aswell.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-02-06 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 16:29 Lucas Stach
2018-01-29 16:29 ` [PATCH 01/10] ARM: import opcode helpers from Linux kernel Lucas Stach
2018-01-29 16:29 ` [PATCH 02/10] ARM: safely switch from HYP to SVC mode if required Lucas Stach
2018-01-29 16:29 ` [PATCH 03/10] ARM: allow secure monitor code to be built without PSCI Lucas Stach
2018-01-29 16:29 ` [PATCH 04/10] ARM: add file for HYP mode related setup Lucas Stach
2018-02-06 12:37 ` Sascha Hauer
2018-01-29 16:29 ` [PATCH 05/10] ARM: don't try to install secure monitor when entered in HYP mode Lucas Stach
2018-01-29 16:30 ` [PATCH 06/10] ARM: default to starting kernel in HYP mode when entered in HYP Lucas Stach
2018-01-29 16:30 ` [PATCH 07/10] ARM: install HYP vectors at PBL and Barebox entry Lucas Stach
2018-01-29 16:30 ` [PATCH 08/10] ARM: rpi: add revision IDs for Pi 3 Model B and Pi Zero Lucas Stach
2018-01-29 16:30 ` [PATCH 09/10] ARM: rpi: add raspberry pi 3 support Lucas Stach
2018-01-29 16:30 ` [PATCH 10/10] ARM: rpi: autosize malloc area Lucas Stach
2018-01-30 11:23 ` [PATCH 00/10] HYP mode handling and RasPi 3 support Roland Hieber
2018-02-06 8:52 ` Sascha Hauer [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=20180206085215.ndvytxn4w32wvyw3@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=l.stach@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