lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 2 Aug 2006 18:59:13 -0400
From:	Theodore Tso <tytso@....edu>
To:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Mathias Adam <a2@...mis.de>
Subject: Re: make 16C950 UARTs work

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ