Sorry for this late reply on the topic, as I've slipped behind a
couple weeks and am constantly playing catch-up here...
welcome to lots of peoples' world.
By all means... please do add the information to the wiki. Even if
any/much of it needs refining and reorganization, that can come
later/sooner. No beagle-related info should be considered "too
good" for the wiki...
When I was getting started, I wanted to learn about the whole boot
sequence and what the heck all the new terms were: MLO, u-boot,
x-loader. I have a better idea now, but this involved reading this
list for weeks with 50+ mails per day before the topic came up in
various posts and was explained with any clarity.
I won't get into how the wiki could better be arranged, as that's
for a different topic, but certainly the info should be in there
somewhere (perhaps add a new page for the info you have and a
one-liner with a link to it on the "beginners" page).
i never suggested that the info wasn't "in there", only that it's
sometimes (often?) very hard to track down. mostly, i wanted to
collect the information i needed to explain how to just get the BB
working *out of the box*, including all the things that could go
wrong (which i think is the most overlooked thing when it comes to
writing up online docs).
by way of explanation, i've spent a lot of years writing linux
courseware and teaching that (and other peoples' courseware), and for
a class to work well, stuff has to *work*. exactly the way it's
explained in the courseware manual.
i spent a lot of time testing labs, and exercises, to make darned
sure that stuff did what it was supposed to do, because there's
nothing more frustrating to a student than typing *exactly* what the
manual says, and having it fail, and having the instructor come over
to some poor sap's terminal, look at it, get a confused look and say,
"hmmmmm ... *that* wasn't supposed to happen." that really kills
classroom productivity.
so it's why i started my beagleboard wiki -- to try to document at
least the first part of the process in such a way that, as long as
someone follows the instructions, they *will* get a working BB. and
if they don't, then i screwed up and should fix what i wrote.
anyway, sorry about rambling on -- it's a bad habit. now i'm
going back to rewrite the section on getting android to run.
rday