From: Jon Smirl <jonsmirl@gmail.com>
To: krishna <krishna.c@globaledgesoft.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to debug kernel before there is no printk mechanism?
Date: Wed, 30 Mar 2005 13:33:24 -0500 [thread overview]
Message-ID: <9e473391050330103379e398de@mail.gmail.com> (raw)
In-Reply-To: <424AD247.4080409@globaledgesoft.com>
Did you try turning on CONFIG_EARLY_PRINTK=y? That will allow printk
to a serial console much earlier.
You need to build the serial driver in too:
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2005-03-30 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 16:22 How to debug kernel before there is no printk mechanism? krishna
2005-03-30 16:47 ` linux-os
2005-03-30 14:54 ` Vicente Feito
2005-03-30 18:09 ` linux-os
2005-03-30 16:16 ` Vicente Feito
2005-03-30 20:11 ` linux-os
2005-03-30 23:31 ` Randy.Dunlap
2005-03-30 18:33 ` 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=9e473391050330103379e398de@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=krishna.c@globaledgesoft.com \
--cc=linux-kernel@vger.kernel.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