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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20060802215958.GA19669@flint.arm.linux.org.uk>
Date:	Wed, 2 Aug 2006 22:59:58 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	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 11:08:56PM +0100, Alan Cox wrote:
> Ar Mer, 2006-08-02 am 15:49 -0400, ysgrifennodd Dave Jones:
> > 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.
> 
> We really ought to do that based on the PCI subvendor/subdevice id of
> the boards in use if possible surely ? It ought to be safe for x86
> because nobody is going to use anything but chip default values so they
> can avoid needing a ROM.

Not correct - there are PCMCIA-based versions of these chips and they
do have weirdo values in the registers to cope with custom crystals
which magically vanish if you reset the UART.

dwmw2's 950-based bluetooth CF card does exactly this.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
-
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/