From: Chuck Ebbert <cebbert@redhat.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Michael Mauch <michael.mauch@gmx.de>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: Serial ports rearranged in 2.6.22?
Date: Tue, 14 Aug 2007 12:14:16 -0400 [thread overview]
Message-ID: <46C1D4D8.2080202@redhat.com> (raw)
In-Reply-To: <200708131633.56908.bjorn.helgaas@hp.com>
On 08/13/2007 06:33 PM, Bjorn Helgaas wrote:
> On Monday 13 August 2007 04:28:00 pm Michael Mauch wrote:
>> 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@gmx.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).
>
> Yes, I messed up the legacy_serial module stuff.
>
>>> 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?
>
> I would not recommend the experimental patch (http://lkml.org/lkml/2007/7/25/455).
> Using the revert patch is probably safest, since it also avoids
> the module load issues.
>
Should that be submitted for 2.6.22-stable?
prev parent reply other threads:[~2007-08-14 16:15 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
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 [this message]
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=46C1D4D8.2080202@redhat.com \
--to=cebbert@redhat.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michael.mauch@gmx.de \
--cc=yhlu.kernel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.