public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Dresser <mdresser@windsormachine.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: DMA !NOT ONLY! for triton again...
Date: Mon, 04 Dec 2000 14:55:15 -0500	[thread overview]
Message-ID: <3A2BF6A2.1BD792BA@windsormachine.com> (raw)
In-Reply-To: <E1430NA-000470-00@the-village.bc.nu>

Well, i just checked ide-dma.c, and the WDC 21600 isn't listed.  31600 is, but no
21600
I've been using the 21600 for awhile now with DMA enabled, under reasonable load,
and it seems to hold up.
Guennadi: I don't suppose you can get your hands on a different size/brand drive
long enough to plug it in, and see if it allows DMA?

Alan Cox wrote:

> Certain older WDC drives are explicitly blacklisted due to firmware bugs.
> WDC put out firmware upgrades but given no answer from them on how to be sure
> a drive was upgraded we play safe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-04 20:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A27C052.EFBA6D6A@windsormachine.com>
2000-12-03 11:00 ` Re[2]: DMA !NOT ONLY! for triton again Guennadi Liakhovetski
2000-12-04 14:35   ` Mike Dresser
2000-12-04 16:01     ` 2.40.t11: Unresolved symbols while insmodding ip_tables Meino Christian Cramer
2000-12-04 17:21     ` Re[2]: DMA !NOT ONLY! for triton again Guennadi Liakhovetski
2000-12-04 17:30       ` Andre Hedrick
2000-12-04 17:58         ` Re[4]: " Guennadi Liakhovetski
2000-12-04 18:29           ` Alan Cox
2000-12-04 19:55             ` Mike Dresser [this message]
2000-12-05 14:30               ` Guennadi Liakhovetski
2000-12-06 13:00                 ` Guennadi Liakhovetski
2000-12-06 19:26                   ` Andre Hedrick

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=3A2BF6A2.1BD792BA@windsormachine.com \
    --to=mdresser@windsormachine.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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