linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	craig48@swbell.net
Subject: Re: ATAPI tape drives broken with libata
Date: Fri, 21 Sep 2007 20:28:31 -0400	[thread overview]
Message-ID: <46F461AF.4020200@rtr.ca> (raw)
In-Reply-To: <20070919215035.1d4557ff@the-village.bc.nu>

Alan Cox wrote:
>> I can read and write the tape successfully, and the written data matches
>> what is later read back from it.
>>
>> Here's the hack I used.  Not ready for mainline, but perhaps it will
>> help Alan or whomever come up with something nice for Jeff.
> 
> Its possible we should just scream and shout but for robustness and
> paranoia I just added ATA_HORKAGE_DRQ and skip the error setup in the
> case that HORKAGE_DRQ is set.
> 
> Just need the identify data now..

I duspect it's *all* ATAPI tape units.  Mine (Conner) is quite a bit older
than the other (Seagate) one that began this thread.  And ide-tape has no
problem with either drive.  Perhaps a whitelist rather than a blacklist here.

Meanwhile, my old Conner tape unit is several hundred miles away from me at present.

Cheers

  reply	other threads:[~2007-09-22  0:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 22:55 ATAPI tape drives broken with libata Chuck Ebbert
2007-08-29 23:50 ` Alan Cox
2007-08-30 16:11   ` Chuck Ebbert
2007-08-31 14:19     ` Alan Cox
2007-09-13 16:35       ` Mark Lord
2007-09-13 18:22         ` Mark Lord
2007-09-13 18:42           ` Mark Lord
2007-09-13 19:07             ` Mark Lord
2007-09-13 19:09               ` Mark Lord
2007-09-19 20:50             ` Alan Cox
2007-09-22  0:28               ` Mark Lord [this message]
2007-09-21  3:07             ` Albert Lee
2007-08-30  4:00 ` Jeff Garzik

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=46F461AF.4020200@rtr.ca \
    --to=liml@rtr.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cebbert@redhat.com \
    --cc=craig48@swbell.net \
    --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).