From: Adam Belay <ambx1@neo.rr.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP Changes for 2.5.72
Date: Thu, 19 Jun 2003 23:42:49 +0000 [thread overview]
Message-ID: <20030619234249.GA31392@neo.rr.com> (raw)
In-Reply-To: <20030619093632.A29602@flint.arm.linux.org.uk>
On Thu, Jun 19, 2003 at 09:36:32AM +0100, Russell King wrote:
> It's purpose is trying to ensure that we don't use an interrupt which
> another serial port is using. Presumably this is because the card does
PnP automatically does this without modification to the rule structure.
> not work, for whatever reason, when it shares interrupts with other serial
> ports.
>
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.
Thanks,
Adam
next prev parent reply other threads:[~2003-06-20 3:52 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 [this message]
2003-06-20 5:55 ` Russell King
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=20030619234249.GA31392@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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