linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Sigler <linux.kernel@free.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Date: Thu, 30 Aug 2007 10:17:13 +0200	[thread overview]
Message-ID: <46D67D09.6090101@free.fr> (raw)
In-Reply-To: <20070829174657.09c7de3c@the-village.bc.nu>

Alan Cox wrote:

> John Sigler wrote:
>
>> Standards:
>>          Likely used: 1
> 
> Prehistory

The tragic bit is that we were sold similar DOMs in 2007...
(It's probably time to change suppliers?)

>>          LBA, IORDY not likely
> 
> No DMA, nothing above PIO2

OK. (Grumble)

>>          Buffer type: 0002: dual port, multi-sector
>>          Buffer size: 1.0kB      bytes avail on r/w long: 4
>>          Cannot perform double-word IO
> 
> Can't even do double word I/O

Double word is 32 bits, right? Isn't "Cannot perform double-word IO" in 
contradiction with the following statements?

  IO_support    =  1 (32-bit)

         Buffer size: 1.0kB      bytes avail on r/w long: 4

(Assuming an 8-bit byte, 4 bytes = 32 bits)

> The messages with old IDE should be harmless and the current libata IDE
> should drive it politely (I debugged a problem the same hardware showed
> up for someone else).

When you say "the current libata IDE" do you mean PATA_VIA (in my case)?
I've avoided this driver because it is marked EXPERIMENTAL. Would there 
be any benefit in using it over the legacy ATA/MFM/RLL driver?

> Basically your dinosaur is working correctly.

What do the warnings mean? :-)

Regards.

  reply	other threads:[~2007-08-30  8:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 16:29 hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } John Sigler
2007-08-29 16:46 ` Alan Cox
2007-08-30  8:17   ` John Sigler [this message]
     [not found]     ` <46D69E03.9080403@vc.cvut.cz>
2007-08-30 12:30       ` John Sigler
2007-08-30 15:10         ` John Sigler
2007-08-30 23:31           ` Alan Cox
2007-08-31  8:22             ` John Sigler
2007-08-31  9:04               ` PROBLEM: kernel 2.6.22.6 pata_pdc202xx_old.c limiting to UDMA/33 instead of UDMA/100 (UPDATED 2.6.22.6) n
2007-09-01 14:58                 ` Sergei Shtylyov
2007-08-31  9:04               ` n
2007-08-31 11:49               ` hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } Alan Cox
     [not found]           ` <311601c90708301534g47b2bca7t77debde058781572@mail.gmail.com>
2007-08-31  8:41             ` John Sigler
2007-09-01 15:48         ` Sergei Shtylyov
2007-08-30 14:05     ` Alan Cox
2007-08-31 20:22   ` Sergei Shtylyov
2007-09-01 15:38 ` Sergei Shtylyov
2007-09-03 13:17   ` John Sigler
2007-09-03 13:40     ` Sergei Shtylyov

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=46D67D09.6090101@free.fr \
    --to=linux.kernel@free.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).