From: n0ano@n0ano.com
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
n0ano@n0ano.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
donald.d.dugger@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Enable console on PCI serial devices
Date: Mon, 20 Oct 2008 11:43:51 -0600 [thread overview]
Message-ID: <20081020174351.GK14490@xolotl.n0ano.com> (raw)
In-Reply-To: <200810201111.08703.bjorn.helgaas@hp.com>
On Mon, Oct 20, 2008 at 11:11:07AM -0600, Bjorn Helgaas wrote:
>...
> It doesn't bother me that the number is large. It's only a factor
> of 16 bigger than the baud rate. It is sort of magic, but on the
> other hand, the number is often printed on a part on the board, so
> it's easy to determine, and fairly easy to document. If you've
> lost the box with the marketing messages on it, I'd argue that it's
> easier to determine the clock rate than the fastest baud rate.
>
> To me it seems more confusing to specify two baud rates: the one
> you want to use, and the fastest one the UART supports.
Well, how about consistency with the current serial driver. The
current driver uses base baud, as evidenced by this code from
`drivers/serial/8250_pci.c':
static struct pciserial_board pci_boards[] __devinitdata = {
[pbn_default] = {
.flags = FL_BASE0,
.num_ports = 1,
.base_baud = 115200,
.uart_offset = 8,
},
I think it's even more important to follow what the driver is
doing. (If I'd lost the bix I would get the PCI IDs and see
what the driver is doing for my unknown card :-)
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@n0ano.com
Ph: 303/443-3786
next prev parent reply other threads:[~2008-10-20 17:44 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
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 [this message]
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=20081020174351.GK14490@xolotl.n0ano.com \
--to=n0ano@n0ano.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=donald.d.dugger@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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®