From: Michael Mauch <michael.mauch@gmx.de>
To: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: Serial ports rearranged in 2.6.22?
Date: Sat, 11 Aug 2007 17:49:25 +0200 [thread overview]
Message-ID: <20070811154925.GA9618@elmicha> (raw)
In-Reply-To: <86802c440708102154r59e1acbj90fa0d5b73197fb9@mail.gmail.com>
Yinghai Lu wrote:
> On 8/10/07, Michael Mauch <michael.mauch@gmx.de> wrote:
> > Hi,
> >
> > 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
> >
> > Is this supposed to be that way? Should we reassign these names with
> > udev? udev-114 doesn't seem to have built-in rules to assign the
> > traditional names.
> >
> > Or could it be related to some brokeness in my BIOS (ACPI/PNP)?
> >
> > I'm using the 8250_pnp module (and it's the same with builtin serial
> > modules). I made sure that I did not accidentally change the BIOS
> > settings for the serial ports.
> >
> > I'm using Gentoo, but on the lirc list was a Fedora user with the same
> > symptoms.
>
> 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
Regards...
Michael
next prev parent reply other threads:[~2007-08-11 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 21:39 Serial ports rearranged in 2.6.22? Michael Mauch
2007-08-11 4:54 ` Yinghai Lu
2007-08-11 15:49 ` Michael Mauch [this message]
2007-08-13 21:34 ` Bjorn Helgaas
2007-08-13 22:28 ` Michael Mauch
2007-08-13 22:33 ` Bjorn Helgaas
2007-08-14 16:14 ` Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070811154925.GA9618@elmicha \
--to=michael.mauch@gmx.de \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox