From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: Scott Wood <scottwood@freescale.com>, ppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: verbose kernel debug
Date: Tue, 29 Jul 2008 20:28:27 -0400 [thread overview]
Message-ID: <9e4733910807291728sc46b19bmbff583a7f494d4a6@mail.gmail.com> (raw)
In-Reply-To: <9e4733910807291717g7096b8eas455964e0bbb637b9@mail.gmail.com>
I finally figured out the right combo to turn it on. I was expecting
it to appear in the "Kernel Debugging" section but it was appearing
down lower.
Seems like this option should be defaulted on no matter what, and then
turn it off to save memory. It was the interaction with
CONFIG_EMBEDDED that confused me.
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2008-07-30 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:47 verbose kernel debug Jon Smirl
2008-07-29 23:05 ` Scott Wood
2008-07-29 23:12 ` Jon Smirl
2008-07-29 23:40 ` Grant Likely
2008-07-30 0:09 ` Jon Smirl
2008-07-30 0:17 ` Jon Smirl
2008-07-30 0:28 ` Jon Smirl [this message]
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=9e4733910807291728sc46b19bmbff583a7f494d4a6@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=scottwood@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).