From: Andrey Panin <pazke@donpac.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP Changes for 2.5.72
Date: Fri, 20 Jun 2003 10:10:20 +0400 [thread overview]
Message-ID: <20030620061020.GC786@pazke> (raw)
In-Reply-To: <20030620065547.B7431@flint.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-20 5:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 23:44 [PATCH] PnP Changes for 2.5.72 Adam Belay
2003-06-18 23:44 ` Adam Belay
2003-06-18 23:45 ` Adam Belay
2003-06-18 23:45 ` Adam Belay
2003-06-18 23:45 ` Adam Belay
2003-06-18 23:46 ` Adam Belay
2003-06-18 23:46 ` Adam Belay
2003-06-18 23:47 ` Adam Belay
2003-06-19 8:36 ` Russell King
2003-06-19 23:42 ` Adam Belay
2003-06-20 5:55 ` Russell King
2003-06-20 6:10 ` Andrey Panin [this message]
2003-06-20 7:10 ` Russell King
2003-06-20 10:03 ` Andrey Panin
2003-06-20 18:00 ` Bill Davidsen
2003-06-21 17:53 ` Thorsten Kranzkowski
2003-06-21 20:26 ` Andrey Panin
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=20030620061020.GC786@pazke \
--to=pazke@donpac.ru \
--cc=linux-kernel@vger.kernel.org \
/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