From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ingo Molnar <mingo@redhat.com>,
anemo@mba.sphere.ne.jp, Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] Import updates from i386's i8259.c
Date: Wed, 06 Dec 2006 16:53:40 +0300 [thread overview]
Message-ID: <4576CB64.2060705@ru.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0612061337220.29000@blysk.ds.pg.gda.pl>
Hello.
Maciej W. Rozycki wrote:
>>>+static struct irq_chip i8259A_chip = {
>>>+ .name = "XT-PIC",
>>>+ .mask = disable_8259A_irq,
>>>+ .unmask = enable_8259A_irq,
>>>+ .mask_ack = mask_and_ack_8259A,
>>> };
>> I wonder whose idea was to call this device XT-PIC. XT never had dual 8259A
>>PICs and so was capable of handling only 8 IRQs. Dual 8259A was first used in
>>the AT class machines...
> Ask Ingo, perhaps... ;-)
Ask and be ignored. :-)
> I think he was perfectly right, though -- this
> is a pair of PC/XT-class PICs.
Coupled as only in PC/AT-class machines. So, this XT qualification is
actually meaningless. It's 8259A, that's all.
> And with the "IO-APIC-edge" and
> "IO-APIC-level" alternatives back when the concept of IRQ controllers was
> introduced, "XT-PIC" rather than "8259A" sounded quite right.
I don't follow you here.
> Maciej
WBR, Sergei
next prev parent reply other threads:[~2006-12-06 13:52 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 [this message]
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
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=4576CB64.2060705@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=anemo@mba.sphere.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.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