From: Jon Smirl <jonsmirl@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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, 5 Sep 2004 22:13:28 -0400 [thread overview]
Message-ID: <9e473391040905191384ace49@mail.gmail.com> (raw)
In-Reply-To: <1094417386.1911.0.camel@localhost.localdomain>
On Sun, 05 Sep 2004 21:49:50 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Nobody else currently needs to attach to it so why make life needlessly
> complicated.
I just read the relevant parts of the ICH manual. This driver is
definitely misnamed. It should be called an "LPC bridge" driver and
moved out of the sound directory. The config words that it is using
control the joystick and midi, but they also control the floppy,
parallel port, serial ports, MSS, SB16, USB, SMbus, IDE, etc.
Shouldn't the BIOS have set these up correctly, does the driver really
need to mess with them?
I also don't see how this is related to hotplug. Just because a LPC
bridge is plugged in doesn't mean that I should immediatle enable
joystick/midi ports, what if I already have those ports on a different
device?
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-06 2:13 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
2004-09-06 2:09 ` Randy.Dunlap
2004-09-06 4:07 ` Jon Smirl
2004-09-06 2:13 ` Jon Smirl [this message]
-- 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=9e473391040905191384ace49@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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