From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Michael Tokarev <mjt@tls.msk.ru>, Adam Belay <ambx1@neo.rr.com>,
matthieu castet <castet.matthieu@free.fr>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: PNP parallel&serial ports: module reload fails (2.6.11)?
Date: Fri, 10 Jun 2005 11:20:44 -0500 [thread overview]
Message-ID: <d120d50005061009206d3cdb53@mail.gmail.com> (raw)
In-Reply-To: <200506101001.40980.bjorn.helgaas@hp.com>
On 6/10/05, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Thursday 09 June 2005 3:16 pm, Russell King wrote:
> > The reason that 8250 first detects your ports is that they're found
> > via the legacy method which is independent of PnP. As you correctly
> > sumise, when you unload 8250_pnp, it disables the device so when you
> > re-load 8250, it's unable to detect your ports using the legacy method.
> >
> > But the legacy method needs to continue to exist for systems which
> > don't have PnP enabled.
>
> But shouldn't we someday move the legacy probing from 8250
> into an 8250_platform and only do it if we don't have 8250_pnp?
>
Given how much pain PNP/ACPI probing of i8042 was causing to everyone
I'd be cautious. BIOS writers are extremely creative. Maybe ia64 only
while x86 should default to legacy probing.
--
Dmitry
next prev parent reply other threads:[~2005-06-10 16:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 22:24 Re:PNP parallel&serial ports: module reload fails (2.6.11)? castet.matthieu
2005-06-03 0:18 ` PNP " Michael Tokarev
2005-06-03 5:58 ` matthieu castet
2005-06-05 10:14 ` matthieu castet
2005-06-05 10:27 ` matthieu castet
2005-06-06 15:01 ` Michael Tokarev
2005-06-06 15:43 ` castet.matthieu
2005-06-06 21:18 ` Adam Belay
2005-06-06 22:43 ` Michael Tokarev
2005-06-08 9:52 ` Adam Belay
2005-06-08 20:29 ` Michael Tokarev
2005-06-08 23:52 ` Adam Belay
2005-06-09 21:07 ` Michael Tokarev
2005-06-09 21:16 ` Russell King
2005-06-10 16:01 ` Bjorn Helgaas
2005-06-10 16:20 ` Dmitry Torokhov [this message]
2005-06-10 16:26 ` Bjorn Helgaas
2005-06-10 16:30 ` Russell King
2005-06-14 19:40 ` Adam Belay
-- strict thread matches above, loose matches on Subject: below --
2005-05-31 23:01 Michael Tokarev
2005-06-01 5:04 ` Andrew Morton
2005-06-01 15:20 ` Michael Tokarev
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=d120d50005061009206d3cdb53@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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