From: Dave Jones <davej@codemonkey.org.uk>
To: linux-ide@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Remove Asus EEE UDMA/33 limitation.
Date: Fri, 2 May 2008 11:44:58 -0400 [thread overview]
Message-ID: <20080502154458.GA10567@codemonkey.org.uk> (raw)
The Asus Eee PC prints this during bootup..
ata2.00: limited to UDMA/33 due to 40-wire cable
Which is unfortunate, as it has..
ata2.00: ATA-4: SILICONMOTION SM223AC, , max UDMA/66
I believe there actually is no cable, and the flash is directly
connected to the controller.
[root@eee ~]# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 64 MB in 3.08 seconds = 20.76 MB/sec
With the patch below it returns..
/dev/sda:
Timing buffered disk reads: 76 MB in 3.04 seconds = 25.04 MB/sec
Signed-off-by: Dave Jones <davej@redhat.com>
--- linux-2.6.24.noarch/drivers/ata/ata_piix.c~ 2008-03-31 23:43:05.000000000 -0400
+++ linux-2.6.24.noarch/drivers/ata/ata_piix.c 2008-03-31 23:44:34.000000000 -0400
@@ -716,6 +716,7 @@ struct ich_laptop {
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 */
--
http://www.codemonkey.org.uk
next reply other threads:[~2008-05-02 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 15:44 Dave Jones [this message]
2008-05-02 16:44 ` Remove Asus EEE UDMA/33 limitation Dave Jones
2008-05-03 9:58 ` Matthew Garrett
2008-05-03 14:51 ` Alan Cox
[not found] <fa.tsKjLRZd5ILFUSCwKgwjuJUvN+Y@ifi.uio.no>
[not found] ` <fa.l6LkASoBXPmhrri16ok+xTRwEUY@ifi.uio.no>
[not found] ` <fa.ulFofhLJhFFkP/xiWxdfjwM8XDA@ifi.uio.no>
2008-05-03 19:34 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080502154458.GA10567@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).