All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Lee <albertcc@tw.ibm.com>
To: Mark Lord <liml@rtr.ca>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org,
	Doug Maxey <dwm@enoyolf.org>, Unicorn Chang <uchang@tw.ibm.com>
Subject: Re: More ATA corner cases
Date: Thu, 17 Aug 2006 10:57:37 +0800	[thread overview]
Message-ID: <44E3DB21.2050105@tw.ibm.com> (raw)
In-Reply-To: <44E3BDB8.2030502@rtr.ca>

Mark Lord wrote:
> Alan Cox wrote:
> 
>> Ar Mer, 2006-08-16 am 18:50 -0400, ysgrifennodd Mark Lord:
>>
>>> Alan Cox wrote:
>>>
>>>> Any objection to me adding a new cable type for "40 wire ATA66 capable"
>>>> to indicate the laptop vendor has been sneaky and we should do full
>>>> UDMA
>>>> ranges regardless of drive or other controller reporting.
>>>
>>> Good.  I'll need that feature for a little mini-ITX box here as well.
>>> It uses a *really short* 40W cable for UDMA4 operation.
>>
>>
>> Can you send me the dmidecode output and the lspci -vxxx for it so I can
>> find something to autodetect this.
> 
> 
> No autodetection possible here -- custom configuration.
> 
> All I need is a modparam or /sys attrib that I can set.
> 

This problem was also seen on the IBM JS20 blade server:
The on-board IDE wires are short enough and capable of UDMA/66, but the
cable detection limits the speed to UDMA/33.
It will be nice to have the "40 wire ATA66 capable" support.

Don't know whether the JS20 can be added to the whitelist automatically.
If Alan is ok, will ask Unicorn's help to sent Alan the dmidecode and
lspci -vxxx data of JS20 (and maybe other blades like HS20/HS40, etc).

--
albert





  reply	other threads:[~2006-08-17  2:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 12:39 More ATA corner cases Alan Cox
2006-08-16 12:27 ` Erik Mouw
2006-08-16 22:50 ` Mark Lord
2006-08-17  0:38   ` Alan Cox
2006-08-17  0:52     ` Mark Lord
2006-08-17  2:57       ` Albert Lee [this message]
2006-08-17  8:28         ` Alan Cox
2006-08-16 22:55 ` 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=44E3DB21.2050105@tw.ibm.com \
    --to=albertcc@tw.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albertl@mail.com \
    --cc=dwm@enoyolf.org \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=uchang@tw.ibm.com \
    /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.