From: Theodore Tso <tytso@mit.edu>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Mathias Adam <a2@adamis.de>
Subject: Re: make 16C950 UARTs work
Date: Wed, 2 Aug 2006 18:59:13 -0400 [thread overview]
Message-ID: <20060802225912.GB30457@thunk.org> (raw)
In-Reply-To: <20060802201723.GC7173@flint.arm.linux.org.uk>
On Wed, Aug 02, 2006 at 09:17:23PM +0100, Russell King wrote:
> On Wed, Aug 02, 2006 at 03:49:38PM -0400, Dave Jones wrote:
> > This patch has been submitted a number of times, and doesn't seem
> > to get any upstream traction, which is a shame, as it seems to work
> > for users, and I keep inadvertantly dropping it from the Fedora
> > kernel everytime I rebase it.
>
> As I've said, I'm ignoring all 950 patches because I don't know what
> works and what doesn't, and it's highly likely that applying one fix
> for one card breaks already working fixes for other cards because
> they have different crystals fitted, thereby requiring different
> register settings.
Actually, this particular one is probably safe, because it doesn't
depend on what crystal is installed, but rather works by using a
documented feature in the Oxford 950 UART to oversample the clock
signal. In addition, the patch only activates UART_TCR if the user
requests the higher baud rates, so the patch only does something if
the user requests a baud rate that would have been previously rejected
by the driver. Worse case, if the UART oscillator is badly
implemented, it might make the UART behave out of spec when supporting
an "overclocked" baud rate, but only when trying to support 234000 bps
on hardware where the stock driver would only support 115200 bps. The
patch programs the UART identically for 115200bps, so it's pretty easy
to prove by inspection that it won't break existing setups.
> Basically, either I need 950 based hardware so I can at least validate
> that new fixes don't break existing setups, or someone else needs to
> be in this position and take on the responsibility for reviewing and
> testing future 950 based patches.
I'll have to wait until I get back home to make sure, but I think have
a 950 based card around somewhere that I'd be happy to give to you on
extended loan. I'm not sure whether I have an PCI card; it might
actually be part of my ISA serial card collection....
- Ted
next prev parent reply other threads:[~2006-08-02 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 19:49 make 16C950 UARTs work Dave Jones
2006-08-02 20:17 ` Russell King
2006-08-02 20:31 ` Dave Jones
2006-08-02 20:47 ` Russell King
2006-08-02 22:59 ` Theodore Tso [this message]
2006-08-07 23:20 ` Mathias Adam
2006-08-09 8:31 ` Russell King
2006-08-02 22:08 ` Alan Cox
2006-08-02 21:59 ` Russell King
2006-08-02 23:28 ` Petr Vandrovec
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=20060802225912.GB30457@thunk.org \
--to=tytso@mit.edu \
--cc=a2@adamis.de \
--cc=davej@redhat.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