linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denny Page <denny@cococafe.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi negotiation problem on aic79xx (39320A) in 2.6.14
Date: Sat, 20 May 2006 10:12:30 -0700	[thread overview]
Message-ID: <446F4DFE.6010201@cococafe.com> (raw)
In-Reply-To: <1148134836.3529.5.camel@mulgrave.il.steeleye.com>

Ok, thanks.  It will be a couple of days before I can do the test.

Denny


James Bottomley wrote:
> On Sat, 2006-05-20 at 08:51 -0500, James Bottomley wrote:
>> On Fri, 2006-05-19 at 22:10 -0700, Denny Page wrote:
>>> Setting the xfer speed in the bios does not appear to affect the
>>> result with
>>> the 2.6.16 kernel.
>> That's odd ... the code to recognise the BIOS settings went into 2.6.16.
>> What does /proc/scsi/aic79xx/<n> say?
> 
> Oh ... actually, I should have traversed the tree rather than going by
> commit date.  Apparently the BIOS code didn't make it in until post
> 2.6.16, so if you check 2.6.17-rc4, it should work.
> 
> James
> 
> 

  reply	other threads:[~2006-05-20 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 22:45 scsi negotiation problem on aic79xx (39320A) in 2.6.14 Michael Stone
2006-03-23 18:09 ` Michael Stone
2006-03-23 18:37   ` James Bottomley
2006-03-24 12:27     ` Michael Stone
2006-03-24 12:30       ` Hannes Reinecke
2006-03-24 12:32         ` Michael Stone
2006-03-24 18:05           ` Stephen Degler
2006-03-24 13:50       ` James Bottomley
2006-05-20  5:10       ` Denny Page
2006-05-20 13:51         ` James Bottomley
2006-05-20 14:20           ` James Bottomley
2006-05-20 17:12             ` Denny Page [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 21:09 Alan D. Brunelle

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=446F4DFE.6010201@cococafe.com \
    --to=denny@cococafe.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@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).