All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@de.bosch.com>,
	Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Dirk Behme <dirk.behme@gmail.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] arm64:renesas: Introduce early console for Salvator-X board
Date: Wed, 9 Nov 2016 12:14:41 +0000	[thread overview]
Message-ID: <a8bf6bbd-803f-58d7-e019-e30907128174@arm.com> (raw)
In-Reply-To: <0399b362-b920-2891-b373-b7a5f6cb9b20@de.bosch.com>

Hello,

On 09/11/16 07:14, Dirk Behme wrote:
> On 08.11.2016 16:41, Iurii Mykhalskyi wrote:
>> Hello Dirk,
>>
>> I have made only single change - I recompile ATF to leave CPU in EL2
>> mode and reflash it.
>
>
> Yes, this is what I meant with 'modifying firmware' ;)
>
> You are loading Xen with U-Boot running in EL2, then?
>
> With this modification, do all other use cases still work? E.g. load and
> boot U-Boot and native Linux kernel without Xen?

Yes, when Linux is booting from EL2, it will drop to EL1 (see 
el2_setup). As Andre mentioned on the previous thread, U-boot is running 
at EL2 on various board (e.g pine64, juno).

Modifying the firmware was the right way to go as there is no solution 
go boot at EL2 from EL1.

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-09 12:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 14:20 [PATCH] arm64:renesas: Introduce early console for Salvator-X board Iurii Mykhalskyi
2016-11-08 14:30 ` Julien Grall
2016-11-08 15:22   ` Dirk Behme
2016-11-08 15:41     ` Iurii Mykhalskyi
2016-11-09  7:14       ` Dirk Behme
2016-11-09 12:14         ` Julien Grall [this message]
2016-11-10  6:54           ` Dirk Behme
2016-11-10  9:25             ` Iurii Mykhalskyi
2016-11-10  9:34               ` Dirk Behme
2016-11-21 17:12                 ` Iurii Mykhalskyi
2016-11-21 17:29                   ` Julien Grall
2016-11-22 10:59                     ` Andrii Anisov
2016-11-22 11:20                       ` Andrii Anisov
2016-11-23 14:00                         ` Iurii Mykhalskyi
2016-11-23 14:15                           ` Andrii Anisov
2016-11-23 14:27                             ` Iurii Mykhalskyi
2016-11-23 14:22                           ` Andrii Anisov
2016-11-25  9:13                             ` Andrii Anisov
2016-11-25 13:44                               ` Iurii Mykhalskyi
2016-11-23 15:04                           ` Julien Grall
2016-11-08 15:48     ` Andrii Anisov

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=a8bf6bbd-803f-58d7-e019-e30907128174@arm.com \
    --to=julien.grall@arm.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=dirk.behme@gmail.com \
    --cc=iurii.mykhalskyi@globallogic.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.