From: Keith Owens <kaos@ocs.com.au>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, len.brown@intel.com,
Andrew Morton <akpm@linux-foundation.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: PNPACPI probes serial twice, messes up serial console
Date: Thu, 22 Mar 2007 15:23:51 +1100 [thread overview]
Message-ID: <11466.1174537431@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 21 Mar 2007 10:35:38 MDT." <200703211035.39340.bjorn.helgaas@hp.com>
Bjorn Helgaas (on Wed, 21 Mar 2007 10:35:38 -0600) wrote:
>On Tuesday 20 March 2007 08:32, Bjorn Helgaas wrote:
>> On Tuesday 20 March 2007 00:46, Keith Owens wrote:
>> > Booting with 'console=tty console=ttyS0,9600'. The serial console on
>> > ttyS0 (0x3f8, irq 4) is probed twice, once from serial8250_init() and
>> > again from serial_pnp_probe().
>>
>> I played with this last summer, but was too timid to finish it
>> and post it. My plan was to remove the legacy SERIAL_PORT_DFNS,
>> make platform devices for them, and only register the platform
>> devices in the absence of PNP.
>>
>> My motivation at the time was to prevent 8250 from claiming IRDA
>> devices that happened to live at legacy UART addresses. I also
>> wanted to make IRDA (smsc-ircc2 in my case) smart enough to use
>> PNP to locate its devices, since 8250 would no longer claim them.
>>
>> Here's the dusty patch (against 2.6.18-rc1-mm2). If it seems
>> like a reasonable thing to do, I can update it, polish it up,
>> add a changelog, and post it.
>
>Keith, does this patch help? Russell didn't complain about it, so
>if it fixes your problem, maybe we could put it in -mm and see if
>it breaks anything else.
The aim of the patch looks sensible, but it will not compile for
2.6.21-rc4. 8250_x86.c tests pnp_platform_devices, which does not
exist. Also the combination of CONFIG_SERIAL_8250_X86=y and
CONFIG_SERIAL_8250_PNP=m would result in 8250_x86.o being built into
vmlinux but referring to serial8250_nopnp in module 8250_pnp.o, kernel
to module references are tricky.
next prev parent reply other threads:[~2007-03-22 4:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 6:46 PNPACPI probes serial twice, messes up serial console Keith Owens
2007-03-20 8:51 ` Russell King
2007-03-20 14:32 ` Bjorn Helgaas
2007-03-20 15:14 ` Russell King
2007-03-21 16:35 ` Bjorn Helgaas
2007-03-21 16:37 ` Russell King
2007-03-21 16:40 ` Bjorn Helgaas
2007-03-24 10:06 ` Russell King
2007-03-22 4:23 ` Keith Owens [this message]
2007-03-22 5:08 ` Bjorn Helgaas
2007-04-06 16:25 ` Bjorn Helgaas
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=11466.1174537431@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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