From: Russell King <rmk@arm.linux.org.uk>
To: Adam Belay <ambx1@neo.rr.com>,
linux-kernel@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH] PnP Changes for 2.5.72
Date: Fri, 20 Jun 2003 06:55:47 +0100 [thread overview]
Message-ID: <20030620065547.B7431@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030619234249.GA31392@neo.rr.com>; from ambx1@neo.rr.com on Thu, Jun 19, 2003 at 11:42:49PM +0000
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?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-06-20 5:41 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 [this message]
2003-06-20 6:10 ` Andrey Panin
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=20030620065547.B7431@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.