public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] use spi_transport_class for aic79xx
Date: Thu, 09 Jun 2005 09:11:42 -0400	[thread overview]
Message-ID: <1118322702.5041.2.camel@mulgrave> (raw)
In-Reply-To: <42A7FD7A.1050105@suse.de>

On Thu, 2005-06-09 at 10:27 +0200, Hannes Reinecke wrote:
> Next step is to connect an U320 drive to check it works properly.

That's definitely a requirement.  The sole function of aic79xx over
aic7xxx is u320.  That being said, I have been covertly converting the
transport classes to cope with u320 DV.  I believe now it all works.
However, you need to plug in more transport parameters than you
currently have (even if a lot of them are read only).  You also need to
update the couplings for the period == 8 case (which is u32).

Let me post the patches I used to fusion as an RFC and you can examine
the variable setting routines to see how it's done 

And I have tested this one:

scsi5 : ioc1: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=56
  Vendor: HP 36.4G  Model: ST336607LW        Rev: HPC3
  Type:   Direct-Access                      ANSI SCSI revision: 03
 target5:0:1: Beginning Domain Validation
 target5:0:1: Ending Domain Validation
 target5:0:1: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS (6.25 ns, offset 127)

James



  reply	other threads:[~2005-06-09 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09  7:08 [PATCH] use spi_transport_class for aic79xx Hannes Reinecke
     [not found] ` <42A7F5A7.5080401@pobox.com>
2005-06-09  8:27   ` Hannes Reinecke
2005-06-09 13:11     ` James Bottomley [this message]
2005-06-09 13:27       ` Hannes Reinecke

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=1118322702.5041.2.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=hare@suse.de \
    --cc=jgarzik@pobox.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