Messages in this thread | | | Date | Fri, 20 Jun 2003 10:10:20 +0400 | Subject | Re: [PATCH] PnP Changes for 2.5.72 | From | Andrey Panin <> |
| |
On 171, 06 20, 2003 at 06:55:47AM +0100, Russell King wrote: > On Thu, Jun 19, 2003 at 11:42:49PM +0000, Adam Belay wrote: > > I removed avoid_irq_share because the current pnp code, like the previous, does > > not allow irq sharing. Also it corrupts the device rule structure by replacing > > it with modified values that may not apply after devices are disabled etc. > > Is there a set of conditions I could follow to determine if a serial pnp device > > is capable of irq sharing, and also with which other devices can a capable > > device share an irq? If so, I could have the resource manager handle this type > > of situation when few irqs are available. > > The problem is one of a lack of historical information on why it was > added. The driver itself allows serial ports to share interrupts between > themselves. Maybe tytso knows why the "Rockwell 56K ACF II Fax+Data+Voice > Modem" is unable to share IRQs?
It was me who added this crappy quirk.
My ELine modem which identified itself "Rockwell 56K ACF II Fax+Data+Voice Modem" was going mad when its IRQ was shared with any device. So I decided to add this quirk.
Personally I think that ISA IRQ sharing should be absolutely last resort technic, because ISA bus was never designed to support IRQ sharing sanely. If you have to enable ISA PnP device and do not have enough IRQ, you must print BIG FAT WARNING before doing this. May be kernel config options must be added for brave guys wanting to use ISA IRQ sharing.
-- Andrey Panin | Linux and UNIX system administrator pazke@donpac.ru | PGP key: wwwkeys.pgp.net [unhandled content-type:application/pgp-signature] | |