All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, Jaroslav Kysela <perex@suse.cz>
Subject: Re: Intel ICH - sound/pci/intel8x0.c
Date: Sun, 5 Sep 2004 11:26:01 -0400	[thread overview]
Message-ID: <9e473391040905082659660d6@mail.gmail.com> (raw)
In-Reply-To: <1094385318.1099.23.camel@localhost.localdomain>

Ok, I can change so I don't have to take ownership of the bridge from
the PCI driver so there isn't a conflict.  "Intel ICH Joystick" is a
deceptive name for this driver. It should be named something like "LPC
bridge" since there are other things on that device than the joystick.
Why does just the joystick need a special driver and nothing else on
that bridge needs one? Wouldn't PS/2, serial, parallel, etc all have
this problem?

"Intel ICH" is also a bad driver name. I'd prefer something like
"snd_intel8x0" since that is what the module is named.

On Sun, 05 Sep 2004 12:55:27 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Also a lot of other vendors Midi and joystick ports do have PCI ids.

I was thinking about this from the probing side. You can't count on
midi and joystick ports having PCI IDs so you have to manually probe.
But I also see how a card with a PCI ID could have these ports on it
and also include logic for turning them off and on.

On Sun, 05 Sep 2004 12:55:27 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Sul, 2004-09-05 at 03:43, Jon Smirl wrote:
> > The joystick PCI ID table in intel8x0.c is not correct. Joysticks and
> > MIDI ports are ISA devices and need be located by manual probing. This
> > ID table needs to be removed. Joystick and MIDI ports do not have PCI
> > IDs.
> 
> It isn't that simple. The LPC bridge also contains the controls for the
> joystick ports. You also need them for hotplug handling of the bridge
> should someone stick one in a laptop docking station. The ID table also
> ensures the driver is loaded. It's probably true that it will need
> splitting up a bit if another driver also needs ownership of the LPC
> bridge but for now that hasn't happened.
> 
> Also a lot of other vendors Midi and joystick ports do have PCI ids.
> 
> Alan
> 
-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2004-09-05 15:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05  2:43 Intel ICH - sound/pci/intel8x0.c Jon Smirl
2004-09-05 11:55 ` Alan Cox
2004-09-05 15:26   ` Jon Smirl [this message]
2004-09-06 10:57 ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2004-09-05 18:48 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
2004-09-06  8:31 Matthieu Castet
2004-09-06 11:27 ` Alan Cox
2004-09-06 14:11   ` Jon Smirl
2004-09-06  8:40 Matthieu Castet
2004-09-06 15:48 Matthieu Castet

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=9e473391040905082659660d6@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 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.