linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: albertl@mail.com
Cc: Jeff Garzik <jgarzik@pobox.com>,
	IDE Linux <linux-ide@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>, Doug Maxey <dwm@maxeymade.com>
Subject: Re: [PATCH 1/1] libata-dev: ata_check_atapi_dma() fix for ATA_FLAG_PIO_POLLING LLDDs
Date: Wed, 15 Mar 2006 11:12:10 -0500	[thread overview]
Message-ID: <44183CDA.5010407@rtr.ca> (raw)
In-Reply-To: <441838B6.8060900@rtr.ca>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

Albert Lee wrote:
> Jeff Garzik wrote:
> 
>> Applied, though I think its an open question what happens with
>> CDB-interrupt ATAPI devices want to do DMA.  Perhaps we just get an
>> interrupt event that we clear, then life proceeds as normal.
> 
> Not sure. I have no such device at hand for test; currently relying
> on the SFF-8020i spec (http://www.bswd.com/sff8020i.pdf) as reference.
> According to p.31, we have to send out the CDB after receiving
> the CDB interrupt. So, just clearing the irq looks not enough.
> 
>> Does anybody actually have such a device anywhere?  :)

Yup, I have two such drives here.

One of them has a grease-pencil "NFG" marking on it,
and other other one doesn't.  They both powered up and
worked just now, and their identify blobs are attached
(you can interpret them with "hdparm --Istdin <blob").

I'm late paying attention on this thread, so what is it
that we wanted done with them?

Or even better, who wants one of them?  Albert, Jeff, or Tejun?

Cheers

[-- Attachment #2: aopen_936e_aku.identify --]
[-- Type: text/plain, Size: 1451 bytes --]


/dev/hdd:
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
85a0 0000 0000 0000 0000 0000 0000 0000
0000 0000 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 0000 0000 0000 5531
3049 2020 2020 4344 2d52 4f4d 2033 3658
2f41 4b55 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 0000
0000 0f00 0000 0400 0200 0006 0000 0000
0000 0000 0000 0000 0000 0000 0000 0107
0003 0078 0096 00e3 0078 0000 0000 0000
0000 0002 0009 3030 3120 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0107 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000

[-- Attachment #3: aopen_940e_aku.identify --]
[-- Type: text/plain, Size: 1451 bytes --]


/dev/hdc:
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
85a0 0000 0000 0000 0000 0000 0000 0000
0000 0000 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 0000 0000 0000 5533
3120 2020 2020 4344 2d52 4f4d 2034 3058
2f41 4b55 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 0000
0000 0f00 0000 0400 0200 0006 0000 0000
0000 0000 0000 0000 0000 0000 0000 0107
0003 0078 0096 00e3 0078 0000 0000 0000
0000 0002 0009 3030 3330 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0107 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0041
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000

  reply	other threads:[~2006-03-15 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  7:57 [PATCH 1/1] libata-dev: ata_check_atapi_dma() fix for ATA_FLAG_PIO_POLLING LLDDs Albert Lee
2006-03-13  8:09 ` Jeff Garzik
2006-03-14  4:52   ` Albert Lee
2006-03-15 15:54     ` Mark Lord
2006-03-15 16:12       ` Mark Lord [this message]
2006-03-15 16:24         ` Mark Lord
2006-03-16  7:22           ` Albert Lee
2006-03-17  5:51             ` Mark Lord
2006-03-15 16:49         ` Mark Lord
2006-04-01 13:24           ` Albert Lee

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=44183CDA.5010407@rtr.ca \
    --to=liml@rtr.ca \
    --cc=albertl@mail.com \
    --cc=dwm@maxeymade.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).