linux-mips
[Top] [All Lists]

Re: Is _do_IRQ() not needed anymore ?

To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: Is _do_IRQ() not needed anymore ?
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Date: Fri, 01 Dec 2006 18:29:17 +0300
Cc: vagabon.xyz@gmail.com, linux-mips@linux-mips.org
In-reply-to: <20061202.002214.51866784.anemo@mba.ocn.ne.jp>
Organization: MontaVista Software Inc.
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <cda58cb80612010206r51d319a1x72105981d900068a@mail.gmail.com> <20061201.191049.63741937.nemoto@toshiba-tops.co.jp> <45704569.8000807@ru.mvista.com> <20061202.002214.51866784.anemo@mba.ocn.ne.jp>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803
Hello.

Atsushi Nemoto wrote:

You can use both irq_cpu and i8259 same time. :)

What's wrong with 8259 I wonder? It's happily converted to genirq by other arches...

Indeed.  I missed other arch's i8259.c had changed.  Maybe we should
update i8259.c entirely.

The question is what flow to use: level/edge ones used in x86 code and actually intended for simplistic controllers, not the likes of 8259 OR the "fasteoi" one used in PowerPC code and (as it turned out in my earlier discussion in linuxppc-dev) intended for the controllers that are smart enough to mask off the lower-priority IRQs when getting the top level one acknowledged and unmask them upon EOI command...

---
Atsushi Nemoto

WBR, Sergei

<Prev in Thread] Current Thread [Next in Thread>