From: "Eric Bénard" <eric@eukrea.com>
To: barebox@lists.infradead.org
Subject: Re: how do i add the defn for the beagle xM to barebox?
Date: Sun, 5 Feb 2012 15:52:01 +0100 [thread overview]
Message-ID: <20120205155201.4086003e@eb-e6520> (raw)
In-Reply-To: <alpine.DEB.2.02.1202050635190.30340@oneiric>
Hi Robert,
Le Sun, 5 Feb 2012 06:52:28 -0500 (EST),
"Robert P. J. Day" <rpjday@crashcourse.ca> a écrit :
> thoughts? i'd actually like to make the tweaks one at a time so
> that the git log shows clearly how the two boards differ one feature
> at a time.
By sensing a few GPIO, you can easily check which board you are running
barebox on and thus have ony binary which supports all beagleboards
(as already done in u-boot).
Check around line 108 in u-boot's beagle support for the details :
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/beagle/beagle.c;h=5c04b34e1ab0140aca93e7752c8672ce7aebc0b9;hb=HEAD
So in the end you can register the nand support only if you run on a
board which has a NAND flash and have one defconfig for all
beagleboards (some tweaks in the clock settings may be nedded -
especially for USB IIRC - as beagle XM is built around a DM3730 which
can run at 1GHz when older beagles had older OMAP3530 limited to
720MHz).
Eric
--
http://eukrea.com/en/news/104-2012
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-05 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 11:52 how do i add the defn for the beagle xM to barebox? Robert P. J. Day
2012-02-05 14:52 ` Eric Bénard [this message]
2012-02-05 14:58 ` Robert P. J. Day
2012-02-05 15:37 ` Robert P. J. Day
2012-02-05 17:43 ` Eric Bénard
2012-02-05 18:00 ` Robert P. J. Day
2012-02-05 19:44 ` Eric Bénard
2012-02-05 21:04 ` Robert P. J. Day
2012-02-06 9:33 ` Eric Bénard
2012-02-06 11:29 ` Sascha Hauer
2012-02-06 11:33 ` 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=20120205155201.4086003e@eb-e6520 \
--to=eric@eukrea.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.