linux-kernel - Re: make 16C950 UARTs work

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 2 Aug 2006 16:31:46 -0400
From:	Dave Jones <davej@...hat.com>
To:	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

Well, thanks for the reply.

 > , 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.

FWIW, we've had that patch in Fedora (most of the time), since 2.6.13,
and I don't recall seeing any other serial breakage ports (on this,
or any UART for that matter).

 > My requests for the broken BT hardware which dwmw2 promised me which
 > the original requests were based upon have consistently resulted in
 > promise of action but no real action.
 > 
 > 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 don't believe that there are sufficient users out there who follow
 > the kernel to allow the "dump in -mm and wait a bit to see if anyone
 > complains" solution will work.

Still, leaving a patch out in the cold for 11 months, when we know it
at least makes things work for some users strikes me as wrong.
If we took this approach with every driver, we'd end up not supporting
the majority of things we support today.

		Dave

-- 
http://www.codemonkey.org.uk
-
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/