From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: inconvenience when hand editing DEBUG_LL in .config
Date: Fri, 20 Jan 2012 17:40:36 +0100 [thread overview]
Message-ID: <20120120164036.GO4066@pengutronix.de> (raw)
Hello,
usually when I want to change a single kernel option I just open .config
in my editor, remove the line for the config item I want to change and
run oldconfig. For DEBUG_LL (defined in arch/arm/Kconfig.debug) this
doesn't work as usual though.
On 3.3-rc1 the following happens:
make ARCH=arm at91rm9200_defconfig
sed -i /CONFIG_DEBUG_LL/d .config
make ARCH=arm oldconfig
The last command then asks me for DEBUG_LL, after specifying 'y', the
output looks as follows:
Verbose user fault messages (DEBUG_USER) [N/y/?] n
Kernel low-level debugging functions (read help!) (DEBUG_LL) [N/y/?] (NEW) y
Kernel low-level debugging port
> 1. No low-level debugging UART (DEBUG_LL_UART_NONE) (NEW)
2. Kernel low-level debugging via EmbeddedICE DCC channel (DEBUG_ICEDCC) (NEW)
3. Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl (AT91_DEBUG_LL_DBGU0) (NEW)
choice[1-3]: 1
Early printk (EARLY_PRINTK) [N/y/?] (NEW)
Note that I didn't specify the '1' for the choice even though all items
are marked as new and oldconfig only starts at EARLY_PRINTK to ask
again.
I would have expected to be able to select AT91_DEBUG_LL_DBGU0.
This is not intended, is it?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next reply other threads:[~2012-01-20 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 16:40 Uwe Kleine-König [this message]
2012-01-20 19:27 ` inconvenience when hand editing DEBUG_LL in .config Russell King - ARM Linux
2012-01-20 23:34 ` Uwe Kleine-König
2012-01-20 20:31 ` Arnaud Lacombe
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=20120120164036.GO4066@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).