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: what is the earliest i can get MLO to print out debugging info?
Date: Fri, 10 Feb 2012 07:59:08 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1202100755520.10458@oneiric> (raw)


  as a (sort of) followup to my last post on extending barebox to
recognize pandaboards, at the moment, i have a build that boots nicely
on an original panda but produces absolutely *no* output at all on a
panda ES.

  i know that barebox currently doesn't recognize the ES, but i'm
wondering if that's the real problem, and where i can put debugging
statements in to show something along the lines of, "hi, i'm just
starting to run MLO".

  surely there's an initial part of MLO that has to run before even
checking the revision of the board, so can i add some debugging that
would show that, or is it not even possible to set up the console
before recognizing the board?  thanks.

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-10 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 12:59 Robert P. J. Day [this message]
2012-02-10 14:35 ` Sascha Hauer

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.1202100755520.10458@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