From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: "panda" config and build doesn't work on panda ES at all
Date: Thu, 9 Feb 2012 09:16:28 +0100 [thread overview]
Message-ID: <20120209081628.GV3852@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1202081718100.26281@oneiric>
On Wed, Feb 08, 2012 at 05:20:45PM -0500, Robert P. J. Day wrote:
>
> just for fun, i configured and built MLO and barebox.bin for the
> panda, then tried to use that on a panda ES -- got no response
> whatever from minicom. i did verify that i could boot to barebox just
> fine on a regular panda, though.
>
> this is different from the case of a regular beagle and beagle xM,
> for which the MLO and barebox.bin boot just fine on an xM, so there's
> clearly a significant difference between those two panda variants as
> far as barebox is concerned. i haven't had any time to look at it in
> more detail yet.
We should add some information about that here:
http://wiki.barebox.org/doku.php?id=boards:texas_instruments_panda
http://wiki.barebox.org/doku.php?id=boards:texas_instruments_beagle
So what variants of these boards are out there?
Panda 'regular'
Panda ES
Beagle 'regular'
Beagle xM
Do these correspond somehow to the revisions printed on the board?
I have a Beagle rev C3 and a Panda rev A1.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-09 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 22:20 Robert P. J. Day
2012-02-09 8:16 ` Sascha Hauer [this message]
2012-02-09 9:18 ` Robert P. J. Day
2012-02-09 10:55 ` Eric Bénard
2012-02-09 10:57 ` Robert P. J. Day
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=20120209081628.GV3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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