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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 05 Aug 2008 02:52:47 +0400
From:	Sergei Shtylyov <sshtylyov@...mvista.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Robert Hancock <hancockr@...w.ca>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ide <linux-ide@...r.kernel.org>
Subject: Re: Kernel Summit request for Discussion of future of ATA (libata)
 and IDE

Hello, I wrote:
>>>>> supported. I couldn't track down where that bit was actually 
>>>>> defined in the first place, all the way back to ATA-1 it seems to 
>>>>> be indicated as reserved. Actually, I'm not sure why the drive 
>>>>> cares in the first place, it would seem like a pure host 
>>>>> controller issue..
>>>>>             
>>>> It goes back before IDE into the depths of the original compaq 
>>>> spec. When
>>>> you have a device wired basically directly to the ISA bus (original 
>>>> IDE)
>>>>         
>>>    ISA has only 8/16-bit data bus, so it could not have mattered 
>>> there...     
>>
>> Depends what a 32bit I/O looks like on the 16bit bus - timing wise.
>>   
>
>   Two 16-bit reads at addresses 0x1x0 and 0x1x2 with the programmed 
> recovery time, IIRC... It's just occured to me that in case of the 
> 16-bit bus it should be how the drive treated the accesses at address 
> 0x1x2 with IOCS16 asserted that could have mattered. If it honored 
> them, 32-bit I/O could have worked even on a dumb ISA "controller", if 
> not -- no way (unless you really had *something* between the ISA and 
> the IDE cable).

    Oh, -IOCS16 is driven by device, not host. I give up then. :-)

MBR, Sergei


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ