From: Wolfgang Denk <wd@denx.de>
To: "Richard Williams" <richard_williams@stratexnet.com>
Cc: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Disabling the serial console upsets CPM UARTS
Date: Thu, 05 Aug 2004 00:47:36 +0200 [thread overview]
Message-ID: <20040804224741.4BDEBC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 05 Aug 2004 09:34:19 +1200." <A3240F62EF3C2749B1A25D3BC9548F4148BC29@ExchWENZ02.wenz.global.vpn>
In message <A3240F62EF3C2749B1A25D3BC9548F4148BC29@ExchWENZ02.wenz.global.vpn> you wrote:
>
> I have seen some questions in the archive about people wanting to disable the serial console but not many answers.
Maybe there ius little to answer?
> We have a custom 860T product running a modified 2.4.4 kernel. The console was disabled by excluding some code in printk.c and this has resulted in strange effects with the CPM UART driver.
Why don't you just pass a "console=null" boot argument?
> My questions are
> 1. Is there a better way to disable the serial console (or even better, allow the kernel parameter 'console=' to switch it on of off)?
Yes, of course there is. "console=null" is all you need.
> 2. If the console port can be changed by the 'console=' parameter, what is the purpose of the compile time configuration and selection of a console port in uart.c?
To set up a default console when no console=... boot argument is present?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"If people are good only because they fear punishment, and hope for
reward, then we are a sorry lot indeed." - Albert Einstein
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-08-04 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 21:34 Disabling the serial console upsets CPM UARTS Richard Williams
2004-08-04 22:47 ` Wolfgang Denk [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=20040804224741.4BDEBC109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=richard_williams@stratexnet.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).