mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Raphaël Poggi" <poggi.raph@gmail.com>
To: barebox@lists.infradead.org
Subject: support of arm64 architecture
Date: Fri, 8 Apr 2016 14:01:21 +0200	[thread overview]
Message-ID: <CACqcpZCMfYE=-5T+m=+fT+TM4gqmPk_6h4AqZoLVSLPL7scBkg@mail.gmail.com> (raw)

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 ?

- 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 ?
      I think UEFI is running at EL3, but I am confused about that,
what is the difference between UEFI and barebox ? Are they both
booloader ? (I guess it is a "noob" question :/)

- I have some issues with malloc, when I use tlsf all malloc failed,
but not with dlmalloc implementation, do you have an idea about this ?


At the moment the current limitations of my port are :
     - MMU not implemented
     - barebox running at EL1
     - barebox env not working
     - only test on qemu

If you want to test it:
https://github.com/raphui/barebox/tree/dev/armv8a_cleanup

I can also send a patch with [RFC] tag is needed.

If you have any suggestions or questions, tell me.

Thank you,

Raphaël Poggi

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

             reply	other threads:[~2016-04-08 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 12:01 Raphaël Poggi [this message]
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

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='CACqcpZCMfYE=-5T+m=+fT+TM4gqmPk_6h4AqZoLVSLPL7scBkg@mail.gmail.com' \
    --to=poggi.raph@gmail.com \
    --cc=barebox@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