From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
vagabon.xyz@gmail.com, linux-mips@linux-mips.org
Subject: Re: [PATCH] Import updates from i386's i8259.c
Date: Thu, 7 Dec 2006 15:09:29 +0000 [thread overview]
Message-ID: <20061207150929.GA4156@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0612071443250.22220@blysk.ds.pg.gda.pl>
On Thu, Dec 07, 2006 at 03:03:48PM +0000, Maciej W. Rozycki wrote:
> > It's not really related as 8259 is programmed to generate vectors 0x20 to
> > 0x2F for x86 but the the IRQs start from zero anyway...
>
> In Linux most platforms define IRQ numbers in the sense of physical lines
> (or wires if you prefer) routed to inputs of interrupt controllers rather
> than vectors which may or may not be used by a given platform (and to
> complicate things further, the presence of which may be
> software-configurable). Of course if a message passing concept is used
> for interrupt delivery (be it a simple chain or a more complicated
> protocol), then a different numbering scheme may be required and exposing
> vectors may be a necessity.
>
> Even with the i8259A there is no need to use its vector at all if the
> processor being interrupted does not issue INTA cycles itself.
The Jazz family and the RM200 have registers to perform interrupt
acknowledge cycles. Linux doesn't use it on the RM200 because of a funny
PCI ASIC bug which may cause certain interrupts getting lost until the
PIC is fully initialized. I never looked into the details since the
SNI recommendation was to just avoid that feature.
Ralf
prev parent reply other threads:[~2006-12-07 15:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 16:23 [PATCH] Import updates from i386's i8259.c Atsushi Nemoto
2006-12-05 16:50 ` Franck Bui-Huu
2006-12-05 16:52 ` Ralf Baechle
2006-12-05 17:10 ` Franck Bui-Huu
2006-12-06 1:28 ` Atsushi Nemoto
2006-12-06 1:45 ` Ralf Baechle
2006-12-05 19:49 ` Ralf Baechle
2006-12-05 19:57 ` Ralf Baechle
2006-12-06 1:39 ` Atsushi Nemoto
2006-12-06 1:58 ` Ralf Baechle
2006-12-06 2:56 ` Atsushi Nemoto
2006-12-06 4:38 ` anemo
2006-12-06 13:17 ` Sergei Shtylyov
2006-12-06 13:48 ` Maciej W. Rozycki
2006-12-06 13:53 ` Sergei Shtylyov
2006-12-06 14:41 ` Maciej W. Rozycki
2006-12-06 15:12 ` Sergei Shtylyov
2006-12-06 15:43 ` Maciej W. Rozycki
2006-12-06 15:48 ` Sergei Shtylyov
2006-12-06 19:00 ` Maciej W. Rozycki
2006-12-06 17:03 ` Atsushi Nemoto
2006-12-06 20:32 ` Ralf Baechle
2006-12-06 12:07 ` Ralf Baechle
2006-12-06 8:40 ` Franck Bui-Huu
2006-12-07 3:17 ` Atsushi Nemoto
2006-12-07 7:34 ` Franck Bui-Huu
2006-12-07 11:50 ` Ralf Baechle
2006-12-07 13:32 ` Maciej W. Rozycki
2006-12-07 13:37 ` Ralf Baechle
2006-12-07 13:51 ` Sergei Shtylyov
2006-12-07 15:03 ` Maciej W. Rozycki
2006-12-07 15:09 ` Ralf Baechle [this message]
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=20061207150929.GA4156@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=sshtylyov@ru.mvista.com \
--cc=vagabon.xyz@gmail.com \
/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