From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: ppc339@vtnet.ca
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ide interrupts
Date: 23 May 2003 18:09:57 +0200 [thread overview]
Message-ID: <1053706196.580.1.camel@gaston> (raw)
In-Reply-To: <200305231136.51119.ppc339@vtnet.ca>
On Fri, 2003-05-23 at 17:36, Trevor Woerner wrote:
> There seems to be a lot of code in the IDE subsystem relating to
> interrupts. Is there a way to set a device in polled (i.e.
> non-interrupt) mode? Maybe some way to run the tasklet/bh periodically?
>
> Does the IDE system want to monitor my ATA device's Ready_NotBusy
> interrupt?
No, linux IDE layer can't do that in a sane way, you are asking for
a _lot_ of trouble... (especially if doing DMA)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-23 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 15:36 ide interrupts Trevor Woerner
2003-05-23 16:09 ` Benjamin Herrenschmidt [this message]
2003-05-25 23:12 ` Trevor Woerner
2003-05-26 6:47 ` Geert Uytterhoeven
2003-05-23 16:26 ` linas
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=1053706196.580.1.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ppc339@vtnet.ca \
/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).