Re: Intel ICH - sound/pci/intel8x0.c

[Matthieu Castet]

> 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.
> 
heu hw_random and i8xx_tco use also the lpc bridge, but hopefully they
don't attach it.
> > 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.
That why I start a patch implementing acpi PnP, but nobody seem
interested :(
> None of them help because you need to deal with hotplug.
Heu, I don't understant why you need to deal with hotplug ?
PnP modules works like pci modules. You make a list of know id, and then
you call {pci,pnp}_{port,irq,dma}_{start,len,...} to access resource of
the device.
Hotplug is need like for pci modules to autoload it.

Also using the LPC brigde the alsa driver don't know about the io port
and irq resource you had to pass them via modules option.
For the gameport, alsa driver use a hardcode value of 0x200 that is
wrong on my computer (it is 0x201).
For the midi port it don't use the irq...
With PnP, the bios/acpi give theses resourse.

For the bit you had to write in the LPC for enable io port, I made a
little test and even if you writte bit that disable the io gameport it
still work. Moreover, I think the bios autoset these bits.

Matthieu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/