From: Ross Biro <rossb@google.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: alan@redhat.com, Stephan von Krawczynski <skraw@ithnet.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-pre4: PDC ide driver problems with shared interrupts
Date: Wed, 05 Feb 2003 09:19:28 -0800 [thread overview]
Message-ID: <3E4147A0.4050709@google.com> (raw)
In-Reply-To: 1044465151.685.149.camel@zion.wanadoo.fr
Benjamin Herrenschmidt wrote:
>While I agree with you here, I don't think it's what's happening.
> /* clear INTR & ERROR flags */
> hwif->OUTB(dma_stat|6, hwif->dma_status);
>
>
>
You have way to much faith in the hardware. Promise is especially known
for not keeping to the spec. I wouldn't trust the interrupt bit to be
valid unless a dma is actually active, i.e. that
hwif->OUTB(hwif->INB(dma_base)|1, dma_base);
has actually been written.
I've actually had a manufacturer tell me that they don't worry about the
spec, just making things work with Windows.
Ross
next prev parent reply other threads:[~2003-02-05 17:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 15:18 2.4.21-pre4: tg3 driver problems with shared interrupts Stephan von Krawczynski
2003-02-02 16:49 ` Jeff Garzik
2003-02-02 17:09 ` Stephan von Krawczynski
2003-02-02 17:15 ` Jeff Garzik
2003-02-02 17:52 ` Stephan von Krawczynski
2003-02-02 18:28 ` Jeff Garzik
2003-02-02 18:31 ` Stephan von Krawczynski
2003-02-03 10:25 ` Stephan von Krawczynski
2003-02-05 9:48 ` 2.4.21-pre4: PDC ide " Stephan von Krawczynski
2003-02-05 11:16 ` Benjamin Herrenschmidt
2003-02-05 11:39 ` Stephan von Krawczynski
2003-02-05 12:21 ` Alan Cox
2003-02-05 12:22 ` Benjamin Herrenschmidt
2003-02-05 12:50 ` Alan Cox
2003-02-05 13:19 ` Stephan von Krawczynski
2003-02-05 12:24 ` Alan Cox
2003-02-05 16:56 ` Ross Biro
2003-02-05 17:12 ` Benjamin Herrenschmidt
2003-02-05 17:19 ` Ross Biro [this message]
2003-02-05 17:34 ` Benjamin Herrenschmidt
2003-02-05 17:38 ` Stephan von Krawczynski
[not found] ` <1044467091.685.155.camel@zion.wanadoo.fr>
2003-02-05 17:58 ` Stephan von Krawczynski
2003-02-05 20:00 ` Bryan Andersen
2003-02-05 19:10 ` Alan Cox
2003-02-06 12:20 ` Stephan von Krawczynski
2003-02-06 23:04 ` Benjamin Herrenschmidt
2003-02-07 9:10 ` Stephan von Krawczynski
-- strict thread matches above, loose matches on Subject: below --
2003-02-05 16:44 Robbert Kouprie
2003-02-05 19:45 ` Bryan Andersen
[not found] <7b263321.0302140626.2ddb7980@posting.google.com>
2003-02-14 14:41 ` Edward King
2003-02-14 15:41 ` Benjamin Herrenschmidt
[not found] <20030202153009$2e0d@gated-at.bofh.it>
[not found] ` <20030205181006$107c@gated-at.bofh.it>
[not found] ` <20030205181006$7bb8@gated-at.bofh.it>
[not found] ` <20030205181006$455c@gated-at.bofh.it>
[not found] ` <20030205181006$5dba@gated-at.bofh.it>
[not found] ` <20030205181006$3358@gated-at.bofh.it>
[not found] ` <200302061451.h16Epl0Z001134@pc.skynet.be>
2003-02-23 14:33 ` Stephan von Krawczynski
2003-02-23 15:04 ` Arjan van de Ven
2003-02-23 17:29 ` Stephan von Krawczynski
[not found] <3F1C54A8.5020404@snarkhunter.com>
2003-07-22 14:44 ` Edward King
2003-07-22 18:07 ` John V. Martinez
2003-07-22 21:02 ` Edward King
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=3E4147A0.4050709@google.com \
--to=rossb@google.com \
--cc=alan@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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