From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jaroslav Kysela <perex@suse.cz>
Subject: Re: Intel ICH - sound/pci/intel8x0.c
Date: Sun, 05 Sep 2004 21:49:50 +0100 [thread overview]
Message-ID: <1094417386.1911.0.camel@localhost.localdomain> (raw)
In-Reply-To: <9e47339104090514244873fd05@mail.gmail.com>
On Sul, 2004-09-05 at 22:24, Jon Smirl wrote:
> I'd don't know enough about the LPC bridge chip to know what the
> correct answer is for this. Right now I tend to think that the PCI
> driver should own the bridge chip. If not the PCI driver then there
> should be an explicit bridge driver. I don' think it is correct that a
> joystick driver is attaching to a bridge chip given the simple fact
Nobody else currently needs to attach to it so why make life needlessly
complicated.
> that all legacy IO - joystick, PS/2, parallel, serial, etc is located
> off from that same bridge chip.
>
> Matthieu's comments about using PNP for this seem to make sense. Are
> we missing implementation of an ACPI feature for controlling these
> ports?
See previous discussion. We have isapnp, biospnp but not great acpi pnp.
None of them help because you need to deal with hotplug.
Alan
next prev parent reply other threads:[~2004-09-05 21:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 18:48 Intel ICH - sound/pci/intel8x0.c Matthieu Castet
2004-09-05 21:24 ` Jon Smirl
2004-09-05 20:49 ` Alan Cox [this message]
2004-09-06 2:09 ` Randy.Dunlap
2004-09-06 4:07 ` Jon Smirl
2004-09-06 2:13 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 15:48 Matthieu Castet
2004-09-06 8:40 Matthieu Castet
2004-09-06 8:31 Matthieu Castet
2004-09-06 11:27 ` Alan Cox
2004-09-06 14:11 ` Jon Smirl
2004-09-05 2:43 Jon Smirl
2004-09-05 11:55 ` Alan Cox
2004-09-05 15:26 ` Jon Smirl
2004-09-06 10:57 ` Takashi Iwai
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=1094417386.1911.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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