From: Baruch Siach <baruch@tkos.co.il>
To: Renaud Barbier <renaud.barbier@ge.com>
Cc: barebox@lists.infradead.org
Subject: Re: bootm
Date: Thu, 6 Oct 2011 15:09:34 +0200 [thread overview]
Message-ID: <20111006130934.GC1494@sapphire.tkos.co.il> (raw)
In-Reply-To: <4E8D870B.8050207@ge.com>
Hi Renaud,
On Thu, Oct 06, 2011 at 11:46:35AM +0100, Renaud Barbier wrote:
> It would be for a ppc.
>
> I am evaluating barebox on a mpc8544.
Can you share your experience with running Barebox on this e500 based chip?
Have you added anything to the generic arch/ppc/ code?
I'm currently working with an e500 based chip (P1011), so I'm very much
interested in your experience.
baruch
> On 06/10/11 08:51, Sascha Hauer wrote:
> >On Wed, Oct 05, 2011 at 03:52:45PM +0100, Renaud Barbier wrote:
> >>Hello,
> >>I am looking for information on how to boot Linux with a device tree.
> >>
> >>Basically, I have a uImage and a device tree(dtb) and with U-boot I
> >>used to do:
> >>bootm uImage_address -- dtb_address
> >>
> >>How does it work with barebox?
> >As Jean-Christophe pointed out the architecture is important. On
> >Arm we do not have devicetree support in any official tree, but
> >I already have patches.
> >
> >Sascha
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-10-06 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 14:52 bootm Renaud Barbier
2011-10-05 19:12 ` bootm Jean-Christophe PLAGNIOL-VILLARD
2011-10-06 7:51 ` bootm Sascha Hauer
2011-10-06 10:46 ` bootm Renaud Barbier
2011-10-06 12:36 ` bootm Sascha Hauer
2011-10-06 13:09 ` Baruch Siach [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=20111006130934.GC1494@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@ge.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