From: Matthias Reichl <hias@horus.com>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-serial@vger.kernel.org>
Subject: Re: OXuPCI952 and baud_base questions
Date: Thu, 2 Dec 2010 00:52:41 +0100 [thread overview]
Message-ID: <20101201235241.GA4070@horus.com> (raw)
In-Reply-To: <20101201221604.GA22114@kroah.com>
Hi Greg!
On Wed, Dec 01, 2010 at 02:16:04PM -0800, Greg KH wrote:
> On Wed, Dec 01, 2010 at 05:46:34PM +0100, Matthias Reichl wrote:
> > I've got a Lindy 51237 multi I/O card (2 16C950 URATs up to 921kbit
> > plus one parallel port) with a Oxford OXuPCI952 chip (PCI vendor
> > ID 0x1415, device ID 0x9505).
> >
> > http://www.lindy-international.com/2-port-rs-232-serial-1-port-parallel-card-pci/51237.html
> > http://www.plxtech.com/products/uart/oxupci952
> >
> > Kernel 2.6.36.1 doesn't contain any device-specific configuration,
> > the "guess code" detects both UARTs at BAR0 and BAR1,
> > but with the wrong baudrate (default of 115200 instead of
> > 921600 needed for this card).
> >
> > The card doesn't report any specific (sub-) vendor/device IDs but
> > the generic Oxford IDs. So adding an entry to the pci_device_id
> > table with a pbn_b0_bt_2_921600 config might break some prior
> > working setups (OXuPCI952 with baud_base=115200).
> >
> > Do you have any policy how to cope with such situations?
>
> Always set the baud rate to a valid one before using the tty port?
Sorry, I meant baud_base (or base_baud in 8250_pci.c), not baudrate :-(
Since the baud_base is differing (115200 instead of 921600)
setting a baudrate of X results in an actual baudrate of X*8 for
this card.
It's no problem for me to do a "setserial ... baud_base=921600"
or pass a module/kernel parameter to circumvent the problem,
but it sure would be nicer if the kernel would have set
the baud_base correctly.
The problem I'm seeing here is that this card is using a stock
OXuPCI952, which can be equipped with any oscillator, and doesn't
report any vendor-specific PCI IDs that lets it be distinguished
from other stock OXuPCI952 cards - otherwise I've just sent
a "[PATCH] Add support for Lindy 51237" to set baud_base=921600
for this specific card.
Personally, all 16C950 (compatible) cards I've bought so far
were capable of a max. 921kbit/sec (and thus had a baud_base of 921600).
So the current default of 115200 doesn't quite match my setup.
If I only need a card capable of 115200 bit/sec I usually buy
a standard 16550 card (not a 16C950).
So, my question is: would you include a patch in the kernel
to change the default baud_base from 115200 to 921600 for
the OXuPCI952 chip (1415:9505)?
so long,
Hias
next prev parent reply other threads:[~2010-12-01 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 16:46 OXuPCI952 and baud_base questions Matthias Reichl
2010-12-01 22:16 ` Greg KH
2010-12-01 23:52 ` Matthias Reichl [this message]
2010-12-01 23:57 ` Greg KH
2010-12-02 0:25 ` Matthias Reichl
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=20101201235241.GA4070@horus.com \
--to=hias@horus.com \
--cc=greg@kroah.com \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).