| 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
| ||
|
Date: Mon, 21 May 2007 12:15:37 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Tejun Heo <htejun@...il.com> Cc: Robert Hancock <hancockr@...w.ca>, linux-kernel <linux-kernel@...r.kernel.org>, ide <linux-ide@...r.kernel.org>, l.genoni@...relinux.com Subject: Re: something strange in libata-core.c for kernel 2.6.22-rc3 > Yeah, that's consistent to what I've seen on my machine which is a > variant of A8N. No matter what value I through at _STM, _GTM just > echoed the result thus always leading to 80c configuration. > > > I guess this means that what we have to do is trust that the BIOS set up > > a reasonable mode and base the cable detect on that (either by reading > > back the boot-up controller registers, or by calling GTM). I imagine > > this is what the Windows default IDE driver is doing (just using the > > boot-up mode and feeding it back using GTM/STM on suspend/resume cycles). > > Alan, what do you think? Interesting, sounds like it is still useful rather than just reading the registers as the GTM/STM seem to survive resume cycles which drive config may not (eg if the driver is loaded after a s2ram/resume. If it just echoes back we should also be able to detect this by using knowingly invalid values. Alan - 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