From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Daniel J Blueman <daniel.blueman@gmail.com>,
Tejun Heo <htejun@gmail.com>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ICH Intel PATA short cable override...
Date: Wed, 05 Sep 2007 22:20:40 -0400 [thread overview]
Message-ID: <46DF63F8.8070805@rtr.ca> (raw)
In-Reply-To: <20070906014209.142382c8@the-village.bc.nu>
Alan Cox wrote:
> On Tue, 4 Sep 2007 13:37:22 +0100
> "Daniel J Blueman" <daniel.blueman@gmail.com> wrote:
>
>> We see that in ata_piix.c, there is a whitelist for (laptop) Intel ICH
>> controllers with short cables, tied to specific vendor subsystem IDs.
>> Since my mini-ITX Ibase MI910F has the subsystem IDs specified as
>> Intel [1], this is unusable.
>>
>> I can't find another existing mechanism to add short cable
>> information, to allow UDMA/66 for my on-board CF socket.
>
> DMI is the other approach (if your box has sane responses to the
> dmidecode command we can do this).
No, something more flexible is needed here.
For example, I have a Mini-ITX server here, which I personally have
equipped with a 3" 40W IDE cable that connects to a notebook drive.
The system currently uses UDMA just fine with the IDE drivers,
but I have not been able to convert it to use the (stock) libata drivers
because of this silly lack of end-user control.
We really need an override for this -- embedded folks would also apprecaate one.
Ditto for selecting transfer modes.
Cheers
next prev parent reply other threads:[~2007-09-06 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 12:37 ICH Intel PATA short cable override Daniel J Blueman
2007-09-05 6:12 ` Andrey Panin
2007-09-06 0:42 ` Alan Cox
2007-09-06 2:20 ` Mark Lord [this message]
2007-09-06 7:59 ` Daniel J Blueman
2007-09-07 23:19 ` Jeff Garzik
2007-09-10 12:15 ` Mark Lord
2007-09-16 7:58 ` Jeff Garzik
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=46DF63F8.8070805@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel.blueman@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.