linux-kernel - Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070831124958.6f2104ec@the-village.bc.nu>
Date:	Fri, 31 Aug 2007 12:49:58 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	John Sigler <linux.kernel@...e.fr>
Cc:	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: hda: set_drive_speed_status: status=0x51 { DriveReady
 SeekComplete Error }

> When a DMA operation is enabled, CS0- and CS1- shall not be asserted and 
> transfers shall be 16-bits wide.
> 
> I took the above to mean the device was designed to support DMA.
> Where did I err?

The bus is specified for DMA, not the device.

> 
> > The data sheet says the media can only do 4.1MB/second which is
> > consistent with only needing PIO2 (actually it's far slower than PIO2)
> 
> Is such a slow speed typical of DOMs sold today?
> 
> Or do DOMs sold today support DMA bus mastering, much higher interface 
> rates, and much higher sustained throughput?

Most CF is pretty slow but the newer CF cards do DMA and are getting far
better.

And yes I'd expect your real time app to deal for 3 or 4mS

(Mind you you'll get 1mS normal operating worst cases off even a fast DMA
IDE disk)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/