From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: how to tell Linux *not* to share IRQs ?
Date: 6 Nov 2001 15:17:12 -0800 [thread overview]
Message-ID: <9s9r1o$388$1@cesium.transmeta.com> (raw)
In-Reply-To: <3B6E44EE000F26DC@mta1n.bluewin.ch> <Pine.LNX.4.31.0108081515300.3853-100000@rc.priv.hereintown.net>
Followup to: <Pine.LNX.4.31.0108081515300.3853-100000@rc.priv.hereintown.net>
By author: Chris Meadors <clubneon@hereintown.net>
In newsgroup: linux.dev.kernel
>
> On Wed, 8 Aug 2001, Per Jessen wrote:
>
> > Yeah - I believe the same was possible on the Z80 - though I'd have to
> > go read the manual to be certain.
>
> It is. When I was reading the description in the previous e-mail, I was
> thinking, "that sounds a lot like the Z80".
>
> I missed the beginning of this thead, what did the so old its new mean?
> Is there a new chip supporting vectored interupts? Or are they just being
> simulated in software?
>
The x86 supports vectored interrupts, too (at least in the same sense
the Z80 does.) There are 256 interrupt vectors possible, 32 of which
are reserved (although that didn't keep IBM from foolishly use them
rather than the 224 that weren't...) However, the PIC architecture in
the PC doesn't use this -- it lets the vectors be generated by the
PIC; the standard dual PIC allows only for 15 vectors and the APIC
something like 24, and it's all controlled by which input line gets
pulled.
Sad, isn't it?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-11-06 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 19:03 how to tell Linux *not* to share IRQs ? Per Jessen
2001-08-08 19:19 ` Chris Meadors
2001-11-06 23:17 ` H. Peter Anvin [this message]
2001-08-09 14:27 ` Andreas Bombe
-- strict thread matches above, loose matches on Subject: below --
2001-07-25 23:23 Scott McDermott
2001-07-25 23:37 ` Alan Cox
2001-07-26 7:06 ` Andrew McNamara
2001-07-26 7:39 ` Chris Wedgwood
2001-08-07 15:09 ` Jes Sorensen
2001-08-08 0:05 ` Andrew McNamara
2001-08-08 11:14 ` Eric W. Biederman
2001-08-08 17:13 ` Mark H. Wood
2001-07-26 7:54 ` Francois Romieu
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='9s9r1o$388$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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