mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: how do i add the defn for the beagle xM to barebox?
Date: Sun, 5 Feb 2012 06:52:28 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1202050635190.30340@oneiric> (raw)


  just about to start reading the barebox docs to see if it's
explained there but here's what i want to do -- i want to specifically
add support for the beagleboard xM to barebox.

  i can see there is already classic beagle support:

http://wiki.barebox.org/doku.php?id=boards:omap

and as a test, i build both the MLO and loader for a *regular* beagle
using barebox and replaced those files in a basic validation image for
the xM.  happily, it booted to the barebox loader, which proves that
the current barebox beagle support represents at least a viable
starting point for the xM.

  there were, of course, some diagnostics based on the differences,
such as:

... snip ...
NAND type unknown: ff,ff
No NAND device found (-19)!
... snip ...

that's not surprising since the beagle has NAND flash while the xM
doesn't, so i'm assuming that my first mod would be something like, in
the xload file, replacing all of:

CONFIG_MTD=y
# CONFIG_MTD_WRITE is not set
# CONFIG_MTD_OOB_DEVICE is not set
CONFIG_NAND=y
# CONFIG_NAND_ECC_SOFT is not set
# CONFIG_NAND_ECC_HW_SYNDROME is not set
# CONFIG_NAND_ECC_HW_NONE is not set
# CONFIG_NAND_INFO is not set
# CONFIG_NAND_BBT is not set
CONFIG_NAND_OMAP_GPMC=y

with:

CONFIG_MTD=n
CONFIG_MAND=n

and in the loader defconfig file, replacing:

CONFIG_MTD=y
CONFIG_NAND=y
CONFIG_NAND_OMAP_GPMC=y

with the same thing, is that it?

  in any event, unless someone has already done this, i'm willing to
start with the existing beagle defconfig files, perhaps even add them
to barebox as is, then start submitting patches that handle the
differences one by one.  is this a reasonable plan?  i'm sure i won't
come up with the final correct defconfig file all in one shot, so i'll
definitely be tweaking and submitting and converging to the correct
solution.

  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.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

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

             reply	other threads:[~2012-02-05 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 11:52 Robert P. J. Day [this message]
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
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=alpine.DEB.2.02.1202050635190.30340@oneiric \
    --to=rpjday@crashcourse.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox