From: Stephen Degler <stephen@degler.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Stephan Rattai <srattai@zmnh.uni-hamburg.de>, linux-scsi@vger.kernel.org
Subject: Re: aic79xx
Date: Mon, 27 Feb 2006 15:20:10 -0500 [thread overview]
Message-ID: <44035EFA.5020602@degler.net> (raw)
In-Reply-To: <1140969107.3692.2.camel@mulgrave.il.steeleye.com>
Hello,
I've observed this problem as well. I'd be happy to test a patch, or
derive one if the patch isn't too involved.
skd
James Bottomley wrote:
>On Wed, 2006-02-22 at 18:39 +0100, Stephan Rattai wrote:
>
>
>>cat /sys/class/spi_transport/target1\:0\:1/min_period
>>6.25
>>
>>2.6.16-rc3 ? Whatever causes this behaviour must have been introduced in
>>2.6.14. The cat above is taken from 2.6.15.4. The output from 2.6.14 is the
>>same (as is the output from /proc/scsi/aic79xx/1), 2.6.16-rc4 dito. 2.6.13
>>was working as expected.
>>
>>
>
>OK, I'm afraid this is a bit more serious than I thought. Apparently
>the aic7xxx code that pulls the settings out of the seeprom didn't get
>ported over to the aic79xx driver.
>
>Temporarily, to achive what you want, you can just do
>
>echo 12.5 > /sys/class/spi_transport/target1\:0\:1/min_period
>echo 1 > /sys/class/spi_transport/target1\:0\:1/revalidate
>
>and that should bring the speed down to U160.
>
>I'll see what it will take to get the seeprom functions ported, but they
>probably won't make 2.6.16.
>
>James
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
prev parent reply other threads:[~2006-02-27 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 15:18 aic79xx Stephan Rattai
2006-02-22 17:14 ` aic79xx James Bottomley
2006-02-22 17:39 ` aic79xx Stephan Rattai
2006-02-26 15:51 ` aic79xx James Bottomley
2006-02-27 12:53 ` aic79xx Stephan Rattai
2006-02-27 20:20 ` Stephen Degler [this message]
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=44035EFA.5020602@degler.net \
--to=stephen@degler.net \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=srattai@zmnh.uni-hamburg.de \
/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).