linux-kernel - Re: Remove Asus EEE UDMA/33 limitation.

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: <20080503095817.GA22208@srcf.ucam.org>
Date:	Sat, 3 May 2008 10:58:17 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Dave Jones <davej@...emonkey.org.uk>, linux-ide@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Remove Asus EEE UDMA/33 limitation.

On Fri, May 02, 2008 at 11:44:58AM -0400, Dave Jones wrote:

>  static const struct ich_laptop ich_laptop[] = {
>  	/* devid, subvendor, subdev */
> +	{ 0x2653, 0x1043, 0x82d8 },	/* ICH6M on Asus Eee PC */
>  	{ 0x27DF, 0x0005, 0x0280 },	/* ICH7 on Acer 5602WLMi */
>  	{ 0x27DF, 0x1025, 0x0102 },	/* ICH7 on Acer 5602aWLMi */
>  	{ 0x27DF, 0x1025, 0x0110 },	/* ICH7 on Acer 3682WLMi */

Don't the ACPI timing methods let us work this out without requiring 
machine specific knowledge? Or is the concern that some firmware will 
let us program high modes even if the cabling isn't up to it?

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/