From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
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 15:27:00 +0200 [thread overview]
Message-ID: <42A843A4.2080702@suse.de> (raw)
In-Reply-To: <1118322702.5041.2.camel@mulgrave>
James Bottomley wrote:
> 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).
A-ha.
Can't say I understood all of it, but nevertheless.
>
> 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
>
That would be helpful. Is it in your recent scsi-misc patch?
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
-
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:[~2005-06-09 13:27 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
2005-06-09 13:27 ` Hannes Reinecke [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=42A843A4.2080702@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@SteelEye.com \
--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