| 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: <51f3faa71002232030u4679b6d0yc8df0679d8e19106@mail.gmail.com> Date: Tue, 23 Feb 2010 22:30:15 -0600 From: Robert Hancock <hancockrwd@...il.com> To: Yuhong Bao <yuhongbao_386@...mail.com> Cc: greg@...ah.com, shane.huang@....com, linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org, tj@...nel.org Subject: Re: SB600 64-bit DMA BIOS misconfiguration (formerly RE: [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support) On Tue, Feb 23, 2010 at 9:53 PM, Yuhong Bao <yuhongbao_386@...mail.com> wrote: > >> it doesn't work. Based on the libata experience with AHCI which has a >> similar 64-bit feature flag, there are some controllers that didn't do >> it properly, but not many (only ATI SB600 it appears, and only on >> certain boards, as it seems it was a BIOS configuration issue). > It seems it was solved by a DMI whitelist, but if it is a BIOS configuration issue, I think it would be better if it could be detected directly instead by reading the configuration directly from the device and correcting it if possible. Is that possible? That would likely be the ideal solution, but only AMD would likely have the info needed to do that, if it's possible.. -- 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