From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Carlo Caione <carlo.caione@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: guruplug/dreamplug porting
Date: Mon, 30 May 2011 11:51:18 +0200 [thread overview]
Message-ID: <20110530095118.GG12442@game.jcrosoft.org> (raw)
In-Reply-To: <4DE355F0.1020502@gmail.com>
On 10:31 Mon 30 May , Carlo Caione wrote:
> Hi,
> I was wondering how feasible it is to port barebox on
> guruplug/dreamplug marvell-based boards.
> The most noticeable problem for me is the initialization part in asm
> (I'm not an asm junkie).
so write it in c
a lots of us do so, Sascha or I mostly write the lowlevel init in C now
as example the generic lowlevel arm init is done in C now
I did it recently on at91rm9200
and will update the at91sam9 to c also
> Is it possible to reuse the arm code (asm)
mostly you can copy it but you will have to put it in the right section
> in the current version of barebox or at least to take it from u-boot
> sources (according to uboot conf files, uboot uses the arm926ejs as
> CPU for the guruplug)?
First do more simple, use barebox as a second stage start by u-boot and then
write the lowloevel init
in barebox we do not have one lowlevel init per armvx but one generic one
so normally the only assembly you could have to write is the
board_lowlevel_init which can be written in C anynway
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-05-30 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 8:31 Carlo Caione
2011-05-30 9:51 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-06-06 8:16 ` Carlo Caione
2011-06-06 9:19 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110530095118.GG12442@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=carlo.caione@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