mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-mm6 libata stupid question...
Date: Fri, 07 Jul 2006 17:12:01 +0100	[thread overview]
Message-ID: <1152288721.20883.12.camel@localhost.localdomain> (raw)
In-Reply-To: <200607070428.k674S8Rf005209@turing-police.cc.vt.edu>

Ar Gwe, 2006-07-07 am 00:28 -0400, ysgrifennodd Valdis.Kletnieks@vt.edu:
> [   34.412761] ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14
> [   34.413426] scsi0 : ata_piix
> [   34.720915] ata1.00: configured for UDMA/33
> [   34.872966] ata1.01: configured for UDMA/33
> There's only one minor detail - although the CD is (AFAIK) a UDMA/33 device,
> the hard drive and the controller are both able to do UDMA/100.

Until the very latest code the speed setting on the libata tree is
conservative and sets the speed per channel not per device. 

The fact you get the same response with drivers/ide rather suggests that
in this case the problem is cable detection. Tweak ata_piix to print out
the cable type it detects. If it thinks its a 40 pin cable you know
where to start.

> Now admittedly, the ide driver wasn't able to figure that out *either*, so
> in a /etc/rc script I had:   '/sbin/hdparm -X udma5'.  But alas, that doesn't
> work:

Right now speed setting by user apps isnt supported.


  parent reply	other threads:[~2006-07-07 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  4:28 Valdis.Kletnieks
2006-07-07  5:33 ` Jeff Garzik
2006-07-07 14:32   ` Valdis.Kletnieks
2006-07-07 18:59   ` Fabio Comolli
2006-07-07 16:12 ` Alan Cox [this message]
2006-07-07 21:22   ` Valdis.Kletnieks
2006-07-07 21:51     ` Alan Cox
2006-07-07 22:05       ` Valdis.Kletnieks

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=1152288721.20883.12.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --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

Powered by JetHome