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:	Tue, 14 Aug 2007 00:28:00 +0200
From:	Michael Mauch <michael.mauch@....de>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
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?

Bjorn Helgaas wrote:

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

Ah, ok, and load the legacy_serial module. Going from built-in serial to
modules I was already challenged to find serial_core, 8250, 8250_pnp
and/or 8250_pci (the help in "make menuconfig" does not seem to show the
help that is written in the Kconfig file for 8250_pnp and 8250_pci).

> 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

Thanks for the information - I wondered how you decided. 

What about 2.6.22.x? Or should the distro kernels use that revert patch
for their stable 2.6.22 kernels?

Regards...
		Michael

-
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