From: "Michael Frank" <mhf@linuxmail.org>
To: "Etienne Lorrain" <etienne_lorrain@yahoo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: Why no interrupt priorities?
Date: Fri, 27 Feb 2004 21:24:25 +0800 [thread overview]
Message-ID: <opr3056zq14evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <20040227113725.12307.qmail@web11808.mail.yahoo.com>
On Fri, 27 Feb 2004 12:37:25 +0100 (CET), Etienne Lorrain <etienne_lorrain@yahoo.fr> wrote:
> Russell King wrote:
>> Michael Frank wrote:
>> > Is this to imply that edge triggered shared interrupts
>> > are used anywhere?
>>
>> It is (or used to be) rather common with serial ports. Remember that
>> COM1 and COM3 were both defined to use IRQ4 and COM2 and COM4 to use
>> IRQ3.
>
> Some unusual hardware could handle two ports on the same IRQ (the
> same card mixing itself the IRQ of the two COM port present on the
> same ISA card) but the mixing could not be reliably handled at the
> ISA level. Using a resistor and/or a diode instead of a jumper to
> select the IRQ could also do the trick. So the software was ready
> to handle two interrupts from two UART on the same IRQ - but you
> had to have special hardware.
I used those cheapy 8 Channel 8250 serial cards and modified them
by oring 8 interrupts to irq 3.
The IRQ was set to level triggered and on an IRQ one polled the
status regs of all 8 channels. That was _just_ OK on a 8MHz 286
at 9600 baud in a custom designed low latency application
(no FIFOS here).
>
> Some people had success having a modem on COM1 and a serial _mouse_
> on COM3 (or the other way around) because the COM1/modem was winning
> the control of the ISA IRQ and the COM3/modem was loosing but because
> of 1200 bauds transmission speed the timer interrupt was recovering the
> char received. So they could not tell the difference and did not know
> why inverting the two serial plug did not work.
:-(
Regards
Michael
next prev parent reply other threads:[~2004-02-27 13:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 11:37 Etienne Lorrain
2004-02-27 13:24 ` Michael Frank [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 17:44 Grover, Andrew
2004-02-27 18:15 ` Chris Friesen
2004-02-27 18:42 ` Richard B. Johnson
2004-02-27 19:42 ` Michael Frank
2004-02-27 19:11 ` Michael Frank
2004-02-27 18:55 ` Matt Mackall
2004-02-27 19:09 ` Tim Hockin
2004-02-27 20:29 ` Matt Mackall
2004-02-27 19:19 ` Michael Frank
2004-02-27 20:53 ` Jesse Pollard
2004-02-29 9:43 ` Michael Frank
2004-03-01 16:57 ` Jesse Pollard
2004-03-01 17:35 ` Michael Frank
2004-03-02 15:25 ` Jesse Pollard
[not found] <mailman.1077822002.21081.linux-kernel2news@redhat.com>
2004-02-27 8:00 ` Pete Zaitcev
2004-02-27 1:36 Grover, Andrew
2004-02-27 3:02 ` Randy.Dunlap
2004-02-29 8:32 ` Michael Frank
2004-02-29 8:36 ` Arjan van de Ven
2004-02-29 9:52 ` Michael Frank
2004-02-27 5:32 ` Benjamin Herrenschmidt
2004-02-27 6:26 ` Michael Frank
2004-02-27 6:46 ` Benjamin Herrenschmidt
2004-02-27 9:05 ` Russell King
2004-02-27 13:31 ` Michael Frank
2004-02-27 13:45 ` Richard B. Johnson
2004-02-27 13:50 ` Russell King
2004-02-27 14:51 ` Michael Frank
2004-02-27 7:25 ` Arjan van de Ven
2004-02-27 10:15 ` Helge Hafting
2004-02-27 18:32 ` Mike Fedyk
2004-02-26 23:47 Albert Cahalan
2004-02-26 19:05 Tim Bird
2004-02-26 19:39 ` Richard B. Johnson
2004-02-26 21:02 ` Tim Bird
2004-02-26 21:30 ` Arjan van de Ven
2004-02-26 22:21 ` Mark Gross
2004-02-27 7:14 ` Arjan van de Ven
2004-02-27 11:27 ` Ingo Oeser
2004-02-27 11:52 ` Arjan van de Ven
2004-02-27 13:23 ` Richard B. Johnson
2004-02-27 12:04 ` Christoph Hellwig
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=opr3056zq14evsfm@smtp.pacific.net.th \
--to=mhf@linuxmail.org \
--cc=etienne_lorrain@yahoo.fr \
--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
all inboxes | Powered by JetHome®