From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John Sigler <linux.kernel@free.fr>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Date: Sat, 01 Sep 2007 00:22:49 +0400 [thread overview]
Message-ID: <46D87899.30006@ru.mvista.com> (raw)
In-Reply-To: <20070829174657.09c7de3c@the-village.bc.nu>
Alan Cox wrote:
>>Standards:
>> Likely used: 1
> Prehistory
>> LBA, IORDY not likely
> No DMA, nothing above PIO2
Cool! :-)
>> 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
I have alwayas wondered what the drive's part in 32-bit I/O... this seems
to be controller's problem exclusively. B-)
WBR, Sergei
next prev parent reply other threads:[~2007-08-31 20:20 UTC|newest]
Thread overview: 19+ 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
[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-08-31 9:04 ` n
2007-08-31 9:04 ` n
2007-09-01 14:58 ` Sergei Shtylyov
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 [this message]
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=46D87899.30006@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.kernel@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.