From: "Yinghai Lu" <yinghai@kernel.org>
To: donald.d.dugger@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Enable console on PCI serial devices
Date: Tue, 14 Oct 2008 15:39:44 -0700 [thread overview]
Message-ID: <86802c440810141539x97ceaa4meaab109fae3d9d4c@mail.gmail.com> (raw)
In-Reply-To: <200810142231.m9EMV95O002974@los-vmm.sc.intel.com>
On Tue, Oct 14, 2008 at 3:31 PM, <donald.d.dugger@intel.com> wrote:
> The problem with using a PCI serial card for the console is that, until
> the PCI serial driver is loaded, output will be lost. The issue is that
> PCI serial devices use a non-standard I/O port address and sometimes use
> a non-standard crystal frequency. This patch gets around those problems
> by allowing you to specify both I/O port address and crystal frequency on
> the kernel command line. The serial console specification is enhanced to be:
>
> BBBBPNF-III/CCC
>
> where BBBB is the baud rate, P is the parity, N is the number of bits,
> F is the flow control, III is the I/O port address (prefix with 0x for
> hexadecimal) and CCC is the crystal frequency. -III and /CCC are optional
> and can be omitted although -III must be specified if you want to set
> /CCC. For example, the option I use is:
>
> console=ttyS0,115200-0xe880/921600
Did you check
console=uart8250,io,0xe880,115200n8
hope you can expand that to support CCC
YH
next prev parent reply other threads:[~2008-10-14 22:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 22:31 donald.d.dugger
2008-10-14 22:39 ` Yinghai Lu [this message]
2008-10-14 23:30 ` n0ano
2008-10-15 9:13 ` Paul Bolle
2008-10-15 20:48 ` n0ano
2008-10-16 10:43 ` Paul Bolle
2008-10-16 16:23 ` Yinghai Lu
2008-10-16 17:12 ` n0ano
2008-10-16 18:19 ` Yinghai Lu
2008-10-16 18:25 ` n0ano
2008-10-16 18:30 ` Yinghai Lu
2008-10-16 18:57 ` n0ano
2008-10-17 2:45 ` n0ano
2008-10-17 3:32 ` Yinghai Lu
2008-10-17 16:05 ` n0ano
2008-10-17 17:01 ` Yinghai Lu
2008-10-14 22:53 ` Alan Cox
2008-10-14 23:04 ` n0ano
2008-10-16 23:16 ` Bjorn Helgaas
2008-10-17 2:39 ` n0ano
2008-10-17 9:28 ` Alan Cox
2008-10-17 14:11 ` n0ano
2008-10-17 14:46 ` Bjorn Helgaas
2008-10-17 15:36 ` n0ano
2008-10-17 16:39 ` Bjorn Helgaas
2008-10-17 17:06 ` n0ano
2008-10-20 16:44 ` Lennart Sorensen
2008-10-20 17:11 ` Bjorn Helgaas
2008-10-20 17:43 ` n0ano
2008-10-20 19:11 ` Bjorn Helgaas
2008-10-21 20:08 ` n0ano
2008-10-21 22:08 ` Bjorn Helgaas
2008-10-21 22:33 ` n0ano
2008-10-17 14:44 ` Bjorn Helgaas
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=86802c440810141539x97ceaa4meaab109fae3d9d4c@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=donald.d.dugger@intel.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
all inboxes | Powered by JetHome®