linux-kernel - Re: [patch] x86, serial: always probe for legacy COM ports

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: <46AA33FF.4070504@garzik.org>
Date:	Fri, 27 Jul 2007 14:05:51 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Russell King <rmk@....linux.org.uk>,
	Adam Belay <ambx1@....rr.com>, Len Brown <lenb@...nel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Sébastien Dugué <sebastien.dugue@...l.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] x86, serial: always probe for legacy COM ports

Bjorn Helgaas wrote:
> Andrew, if you drop
>     revert-x86-serial-convert-legacy-com-ports-to-platform-devices.patch
> and apply this, we should have the previous behavior.  I think the
> conversion to platform devices is still worthwhile.  Obviously, I intend
> this as 2.6.23 material.
> 
> 
> Always probe for serial ports at legacy addresses, even if we have PNPBIOS
> or ACPI that should tell us about those ports.
> 
> We have no reports yet of defective firmware that completely omits ports.
> However, Sébastien Dugué <sebastien.dugue@...l.net> reported that the
> NEC Express5800/120Lh with Phoenix BIOS 6.0.5N52, released 7/12/2005,
> reports COM2 first, then COM1 in the ACPI namespace.
> 
> 8250_pnp currently registers devices in namespace order.  On this machine,
> that makes ttyS0=COM2 and ttyS1=COM1, the reverse of what we want.
> 
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@...com>

This is still incomplete, as repeatedly stated.  Here is the email, again.

	Jeff




Download attachment "Attached Message" of type "message/rfc822" (2058 bytes)