From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: how does one enable barebox's low-level debugging?
Date: Mon, 3 Dec 2012 12:46:58 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1212031243060.27270@oneiric> (raw)
In-Reply-To: <20121203162121.GT10369@pengutronix.de>
On Mon, 3 Dec 2012, Sascha Hauer wrote:
> On Mon, Dec 03, 2012 at 10:45:41AM -0500, Robert P. J. Day wrote:
> >
> > looking through common/startup.c and decided i wanted to see
> > confirmation of all the initcalls running here:
> >
> > for (initcall = __barebox_initcalls_start;
> > initcall < __barebox_initcalls_end; initcall++) {
> > debug("initcall-> %pS\n", *initcall);
> > result = (*initcall)();
> > if (result)
> > pr_err("initcall %pS failed: %s\n", *initcall,
> > strerror(-result));
> > }
> >
> >
> > so i started from scratch, ran "make menuconfig" for both the x-loader
> > and barebox to enable "low level debug messages", but i don't see any
> > difference in the boot output.
> >
> > i've perused the barebox wiki and don't see anything regarding that
> > setting. am i doing something wrong?
>
> You have to add a "#define DEBUG" to the file you want to have the
> debug messages from. Add this *above* the includes, just like in the
> kernel.
ah, got it ... for some reason, i thought it was that menuconfig
setting that was responsible but now i see they're actually
independent features.
so, as i read it, using "#define DEBUG" causes this to kick in for a
given source file:
#ifdef DEBUG
#define pr_debug(fmt, arg...) printf(fmt, ##arg)
#else
#define pr_debug(fmt, arg...) do {} while(0)
#endif
#define debug(fmt, arg...) pr_debug(fmt, ##arg)
while that menuconfig setting for "low-level messages" defines
operations for these (totally independent of DEBUG, right?)
# define PUTC_LL(c) do {} while (0)
# define PUTHEX_LL(v) do {} while (0)
# define PUTS_LL(c) do {} while (0)
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
next prev parent reply other threads:[~2012-12-03 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 15:45 Robert P. J. Day
2012-12-03 16:21 ` Sascha Hauer
2012-12-03 17:46 ` Robert P. J. Day [this message]
2012-12-04 11:52 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-04 12:10 ` Robert P. J. Day
2012-12-04 16:33 ` Jean-Christophe PLAGNIOL-VILLARD
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.1212031243060.27270@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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