mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: "Raphaël Poggi" <poggi.raph@gmail.com>, barebox@lists.infradead.org
Subject: Re: support of arm64 architecture
Date: Fri, 08 Apr 2016 23:05:06 +0200	[thread overview]
Message-ID: <1460149506.25419.4.camel@lynxeye.de> (raw)
In-Reply-To: <CACqcpZCMfYE=-5T+m=+fT+TM4gqmPk_6h4AqZoLVSLPL7scBkg@mail.gmail.com>

Am Freitag, den 08.04.2016, 14:01 +0200 schrieb Raphaël Poggi:
> Hi all,
> 
> I am working on porting barebox on arm64 architecture.
> 
> So I have some questions about it:
> 
> - Is there any interest for barebox to support this architecture ?
> 
Now that I have an actually interesting ARMv8 system myself I would
like to see some architecture support land in barebox.

> - My port is running at EL1 for the moment, does the bootloader have
> to run at EL3 ? If yes, do you have hint to achieve this ?

Depending on your system setup both is a valid thing. If you have a
full blown firmware hypervisor below barebox EL1 is okay.

Though normally barebox is the system firmware itself, in which case it
must be able to run at EL3 to provide all system services including
duties of the secure monitor. If there is only a secure monitor below,
barebox may be started in EL2.

Regards,
Lucas

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2016-04-08 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 12:01 Raphaël Poggi
2016-04-08 17:30 ` Sascha Hauer
2016-04-11  6:49   ` Raphaël Poggi
2016-04-13 10:56     ` Sascha Hauer
2016-04-08 21:05 ` Lucas Stach [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=1460149506.25419.4.camel@lynxeye.de \
    --to=dev@lynxeye.de \
    --cc=barebox@lists.infradead.org \
    --cc=poggi.raph@gmail.com \
    /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