All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] aic79xx: fix up transport settings
Date: Thu, 04 Aug 2005 08:58:14 +0200	[thread overview]
Message-ID: <42F1BC86.8070204@suse.de> (raw)
In-Reply-To: <1123093511.5019.17.camel@mulgrave>

James Bottomley wrote:
> There's a slight problem in the way you've done the transport
> parameters; reading from the variables actually produces the current
> settings, not the ones you just set (and there's usually a lag because
> devices don't renegotiate until the next command goes over the bus).  If
> you set the bit immediately, you get into the situation where the
> transport parameters report something as being set even if the drive
> cannot support it.
> 
Well, as usual you're correct. I wasn't quite sure as to _when_ the
transport class parameter will be set, as they appearently haven't been
set correctly (this was whilst chasing down the ST/DT setting issue).
But yours if of course the correct way of doing things.

> I patched the driver to do it this way and also corrected a panic in the
> proc routines.
> 
THX. Didn't even know there was a proc panic :-).

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		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

      reply	other threads:[~2005-08-04  6:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 18:25 [PATCH] aic79xx: fix up transport settings James Bottomley
2005-08-04  6:58 ` 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=42F1BC86.8070204@suse.de \
    --to=hare@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.