linux-kernel - Re: Serial ports rearranged in 2.6.22?

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:	Mon, 13 Aug 2007 15:34:14 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Michael Mauch <michael.mauch@....de>
Cc:	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
	"Yinghai Lu" <yhlu.kernel@...il.com>
Subject: Re: Serial ports rearranged in 2.6.22?

On Saturday 11 August 2007 09:49:25 am Michael Mauch wrote:
> Yinghai Lu wrote:
> 
> > On 8/10/07, Michael Mauch <michael.mauch@....de> wrote:
> > > until 2.6.21, I had the normal assignments for ttyS0 and ttyS1:
> > >
> > > 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> > > 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > >
> > > With 2.6.22 I get the names <-> ports/irqs the other way around:
> > >
> > > 00:08: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A
> > > 00:09: ttyS1 at I/O 0x3f8 (irq = 4) is a 16550A
> > > ...
> > http://lkml.org/lkml/2007/7/25/455
> 
> Thanks - I applied that patch and the names are back to normal again:
> 
> 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 00:07: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

Just FYI, the patch Yinghai mentioned above was experimental, and
we decided it was the wrong solution.

For 2.6.22, the easiest workaround is to boot with the 
"legacy_serial.force" option.

For 2.6.23, we reverted my patch that caused the names to be swapped:
  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=57d4810ea0d9ca58a7bcc1336607f0cede0a2abf

Bjorn
-
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/