mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: barebox@lists.infradead.org
Subject: Re: how do i add the defn for the beagle xM to barebox?
Date: Sun, 5 Feb 2012 20:44:43 +0100	[thread overview]
Message-ID: <20120205204443.60ee2afa@eb-e6520> (raw)
In-Reply-To: <alpine.DEB.2.02.1202051257100.13319@oneiric>

Le Sun, 5 Feb 2012 13:00:13 -0500 (EST),
"Robert P. J. Day" <rpjday@crashcourse.ca> a écrit :

> On Sun, 5 Feb 2012, Eric Bénard wrote:
> 
> > This is the case where u-boot is built with SPL thus reoplacing
> > x-load : they always read NAND ID as some XM boards were mounted
> > with Numonyx POP which includes NAND and 166MHz RAM when mot XM
> > boards have a POP with only 200MHz DDR (and in that case
> > manufacturer ID is 0). So even on a XM you need to check the NAND ID
> > to set the right RAM settings.
> 
>   ah, got it.  but what about in a more general case?  what if you
> have a current, accurate definition for an existing board?  then a
> *slight* variant of that board comes along, for which some settings in
> the defconfig file are simply wrong?
> 
>   are there any examples of that in barebox right now?  and if not,
> how would one handle them?  put another way, what if *all* xM boards
> had no NAND?  then we'd be back to my original question, and it's
> still not clear how you'd define that new board for barebox.
> 
if no XM board had NAND, you would simply check the board type using the
GPIO sampled and you wouldn't register the nand (line 305 in
board-beagle.c) and the fact that the nand driver is enabled is not a
problem if the device is not registrered the driver won't be used.

Eric
-- 
http://eukrea.com/en/news/104-2012

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

  reply	other threads:[~2012-02-05 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 11:52 Robert P. J. Day
2012-02-05 14:52 ` Eric Bénard
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 [this message]
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=20120205204443.60ee2afa@eb-e6520 \
    --to=eric@eukrea.com \
    --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