linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Cc: Sven.Dickert@planb.de, davidm@amberdata.demon.co.uk,
	geert@linux-m86k.org, hollis@austin.ibm.com, paubert@iram.es
Subject: Re: RFC: i8259.c cleanup
Date: Wed, 7 Nov 01 15:00:35 PST	[thread overview]
Message-ID: <0111072300.AA06602@ivan.Harhan.ORG> (raw)


Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> But because you have 2 cascaded i8259s it's more complex to poll both i8259s
> than to read the single magic interrupt acknowledge register.

True, an Interrupt Acknowledge cycle is more efficient than polling. I guess we
could make two versions of the 8259 code, one using the more efficient
Interrupt Acknowledge cycle and the other using polling for machines that don't
support interrupt acknowledge.

MS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-11-07 23:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 23:00 Michael Sokolov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-07 23:04 RFC: i8259.c cleanup Michael Sokolov
2001-11-07 22:55 Michael Sokolov
2001-11-07 22:43 Michael Sokolov
2001-11-07 21:22 Michael Sokolov
2001-11-07 21:26 ` Geert Uytterhoeven
2001-11-07 21:13 Michael Sokolov
2001-11-07 21:22 ` Geert Uytterhoeven
2001-11-07 20:31 Michael Sokolov
2001-11-07  4:43 Michael Sokolov
2001-11-07  6:31 ` Dag Nygren
2001-11-07  7:00   ` Dan Malek
2001-11-07  7:09     ` Dag Nygren
2001-11-07  6:38 ` Dan Malek
2001-11-06 23:15 hollis
2001-11-07  6:37 ` Dan Malek
2001-11-07  9:31   ` Geert Uytterhoeven
2001-11-07  9:40     ` Gabriel Paubert
2001-11-07  9:38 ` Gabriel Paubert
2001-11-07 17:06   ` hollis
2001-11-07 17:17     ` Geert Uytterhoeven
2001-11-07 21:17     ` Gabriel Paubert
2001-11-07 22:01       ` hollis
2001-11-07 20:46 ` Val Henson

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=0111072300.AA06602@ivan.Harhan.ORG \
    --to=msokolov@ivan.harhan.org \
    --cc=Sven.Dickert@planb.de \
    --cc=davidm@amberdata.demon.co.uk \
    --cc=geert@linux-m86k.org \
    --cc=hollis@austin.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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;
as well as URLs for NNTP newsgroup(s).