Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: vagabon.xyz@gmail.com, linux-mips@linux-mips.org
Subject: Re: Is _do_IRQ() not needed anymore ?
Date: Fri, 01 Dec 2006 18:29:17 +0300	[thread overview]
Message-ID: <45704A4D.9050303@ru.mvista.com> (raw)
In-Reply-To: <20061202.002214.51866784.anemo@mba.ocn.ne.jp>

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

  reply	other threads:[~2006-12-01 15:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01  9:40 Is _do_IRQ() not needed anymore ? Franck Bui-Huu
2006-12-01  9:57 ` Atsushi Nemoto
2006-12-01 10:06   ` Franck Bui-Huu
2006-12-01 10:10     ` Atsushi Nemoto
2006-12-01 10:19       ` Franck Bui-Huu
2006-12-01 10:41         ` Atsushi Nemoto
2006-12-01 11:03           ` Franck Bui-Huu
2006-12-01 11:12             ` Franck Bui-Huu
2006-12-01 11:12             ` Atsushi Nemoto
2006-12-01 15:08       ` Sergei Shtylyov
2006-12-01 15:22         ` Atsushi Nemoto
2006-12-01 15:29           ` Sergei Shtylyov [this message]
2006-12-01 15:34             ` Sergei Shtylyov

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=45704A4D.9050303@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --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