| 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
| ||
|
Message-ID: <b2b2f2320812031908se18efdft1a94cb2b158f540e@mail.gmail.com> Date: Wed, 3 Dec 2008 21:08:30 -0600 From: "Shane McDonald" <mcdonald.shane@...il.com> To: "Sergei Shtylyov" <sshtylyov@...mvista.com> Cc: "Alan Cox" <alan@...rguk.ukuu.org.uk>, bzolnier@...il.com, linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Resurrect IT8172 IDE controller driver On Mon, Nov 24, 2008 at 7:38 AM, Sergei Shtylyov <sshtylyov@...mvista.com> wrote: > Hello. > > Alan Cox wrote: > >>>> It's 240, not 242 ns as 33 is actually 33.333. > >>> The maximum values give cycle time of 480 ns menaing that the controller >>> doesn't support PIO mode 0. Hm... > >> Even if you clear the enable for the timing register ? > > These fast timing bits are documented as reserved. The spec says that PIO mode 0 is supported, but Sergei is correct -- the maximum values give a cycle time of 480 ns. How can this be? The old driver appeared to have tried to support PIO mode 0 by setting to the maximum. Which fast timing bits are documented as reserved? My spec has the IDE Drive 0/1 Recovery Time and IDE Drive 0/1 Pulse Width bits in it. Are there other timing bits that aren't documented in my spec? Please excuse my dumb question -- I'm a little over my head here. >> Alan > > MBR, Sergei Shane -- 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/
Powered by blists - more mailing lists