From: Kurt Garloff <garloff@suse.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: IDE-SCSI/HPT366 Problem
Date: Thu, 30 Nov 2000 13:12:37 +0100 [thread overview]
Message-ID: <20001130131237.F7894@garloff.etpnet.phys.tue.nl> (raw)
In-Reply-To: <20001129225210.A10380@bastion.sprileet.net> <Pine.LNX.4.10.10011292210320.1035-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10011292210320.1035-100000@master.linux-ide.org>; from andre@linux-ide.org on Wed, Nov 29, 2000 at 10:25:45PM -0800
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Hi Andre,
On Wed, Nov 29, 2000 at 10:25:45PM -0800, Andre Hedrick wrote:
> If you want to run it under PIO mode and not do DMAing then it will work.
> Also it goes for any device that does ATAPI DMA and not ATA DMA.
> There is a difference!
Could you work out this a little bit to make ot more clear?
What's the difference between ATAPI DMA and ATA DMA?
Is this a controller(chipset) or a device thing?
What controllers or devices are affected?
Is this only a problem for mixing such things on the same bus? The same
controller?
It boils down to one question:
What do the users have to avoid?
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-11-30 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 19:06 --Damacus Porteng--
2000-11-29 18:14 ` Kurt Garloff
2000-11-29 18:20 ` James A Sutherland
2000-11-29 18:27 ` Andre Hedrick
2000-11-30 4:52 ` Damacus Porteng
2000-11-30 6:25 ` Andre Hedrick
2000-11-30 12:12 ` Kurt Garloff [this message]
2000-11-30 1:08 ` Mike A. Harris
2000-11-29 18:23 ` 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=20001130131237.F7894@garloff.etpnet.phys.tue.nl \
--to=garloff@suse.de \
--cc=andre@linux-ide.org \
--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
all inboxes | Powered by JetHome®