From: Jeremy Higdon <jeremy@sgi.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Mikael Starvik <mikael.starvik@axis.com>,
Erik Jacobson <erikj@subway.americas.sgi.com>
Subject: Re: [patch][2/3] ide: add ide_hwif_t->dma_exec_cmd()
Date: Mon, 13 Sep 2004 15:31:37 -0700 [thread overview]
Message-ID: <20040913223137.GB95391@sgi.com> (raw)
In-Reply-To: <200409140011.22047.bzolnier@elka.pw.edu.pl>
On Tue, Sep 14, 2004 at 12:11:21AM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Monday 13 September 2004 23:35, Jeremy Higdon wrote:
> > > Some real bugs are also fixed:
> > > - in Etrax ide.c driver REQ_DRIVE_TASKFILE requests weren't
> > > handled properly for drive->addressing == 0
> > > - in trm290.c read and write commands were interchanged
> > > - in sgiioc4.c commands weren't sent to disk devices
>
> DMA commands, PIO ones were sent out
>
> > Sgiioc4 only is used with multimedia devices. I don't think disks will
> > work with it, even if you do send commands.
>
> It is hard to believe but if this is true it should be documented somewhere.
>
> Anyway my changes don't make it worse. :-)
Okay. I just wanted to be sure you knew. It would be a challenge
just to connect a disk to it, so it probably doesn't matter too much.
Even if you did and it worked, Multimode 2 DMA speeds would not be
too exciting . . . . :-)
prev parent reply other threads:[~2004-09-13 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 23:33 [patch][2/3] ide: add ide_hwif_t->dma_exec_cmd() Bartlomiej Zolnierkiewicz
2004-09-13 21:35 ` Jeremy Higdon
2004-09-13 22:11 ` Bartlomiej Zolnierkiewicz
2004-09-13 22:31 ` Jeremy Higdon [this message]
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=20040913223137.GB95391@sgi.com \
--to=jeremy@sgi.com \
--cc=bzolnier@elka.pw.edu.pl \
--cc=erikj@subway.americas.sgi.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.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;
as well as URLs for NNTP newsgroup(s).