how do i add the defn for the beagle xM to barebox?
Robert P. J. Day
rpjday at crashcourse.ca
Sun Feb 5 06:52:28 EST 2012
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:
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,
... 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_WRITE is not set
# CONFIG_MTD_OOB_DEVICE is not set
# 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
and in the loader defconfig file, replacing:
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
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.
Robert P. J. Day Ottawa, Ontario, CANADA
More information about the barebox