linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: libata-dev#upstream pdc_adma fails IDENTIFY w/ AC_ERR_HSM
Date: Fri, 04 Aug 2006 12:09:13 -0400	[thread overview]
Message-ID: <44D37129.9030100@rtr.ca> (raw)
In-Reply-To: <44D36823.7020406@pobox.com>

Jeff Garzik wrote:
> Tejun Heo wrote:
>> [adma_intr_mmio      ] ata1: protocol 2 (dev_stat 0x58)
>> [ata_port_flush_task ] ENTER
>> [ata_port_flush_task ] flush #1
>> ata1: ata_port_flush_task: flush #2
>> ata1: ata_port_flush_task: EXIT
>> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x2)
> 
> 
> AC_ERR_HSM comes from the call to ac_err_mask().  Given a Status of 
> 0x58, it would appear that DRQ is asserted.
> 
> So if I had to guess, I would say that the above interrupt is the 
> DRQ-is-asserted indication, which would imply perhaps that this driver 
> should not bother with PIO polling.

I think this illustrates just how few people (Tejun) actually have
these chips and use them with Linux.  :)

I don't have a system to test this with today (long story),
but I'm trying to piece one together for later.

Is this "IDENTIFY using IRQs rather than polling" a newish feature?
Because I just don't see how it could work with the the existing
adma_intr_mmio routine --> that code is only correct for non-data
commands, and IDENTIFY definitely has data.

Borken driver, for sure.

  reply	other threads:[~2006-08-04 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 12:00 libata-dev#upstream pdc_adma fails IDENTIFY w/ AC_ERR_HSM Tejun Heo
2006-08-04 13:56 ` Mark Lord
2006-08-04 14:18   ` Tejun Heo
2006-08-04 15:02     ` Tejun Heo
2006-08-04 15:30 ` Jeff Garzik
2006-08-04 16:09   ` Mark Lord [this message]
2006-08-04 16:26     ` Tejun Heo
2006-08-08  6:18       ` Albert Lee
2006-08-09  9:30         ` Tejun Heo

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=44D37129.9030100@rtr.ca \
    --to=liml@rtr.ca \
    --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).