From: James Bottomley <James.Bottomley@steeleye.com>
To: Jonathan McDowell <noodles@earth.li>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Patch for reset in ini9100u [Initio 9100U(W)]
Date: 07 Jan 2004 18:56:04 -0600 [thread overview]
Message-ID: <1073523364.1883.12.camel@mulgrave> (raw)
In-Reply-To: <20040106231426.GR1845@earth.li>
On Tue, 2004-01-06 at 17:14, Jonathan McDowell wrote:
> I have an IWill 2935UW SCSI controller which uses the ini9100u driver.
> This has been working fine under 2.4 but I've recently built up a box of
> spare bits including the controller and installed 2.6 on it. The driver
> is marked broken in 2.6, apparently because of a lack of reset/abort
> functionality as it compiles and runs ok. So I've taken a stab at
> getting reset support back. Patch is below and it's received minimal
> testing - it boots, removes the callback trace and error message and
> doesn't seem to cause problems (the only disk in the machine is on this
> card).
I think it's a good beginning. However, there are some things that
could be done to improve it.
> +int i91u_bus_reset(Scsi_Cmnd * SCpnt)
> +{
> + HCS *pHCB;
> +
> + pHCB = (HCS *) SCpnt->device->host->base;
> + tul_reset_scsi_bus(pHCB);
This won't quite do beacuse tul_reset_scsi_bus() has some really nasty
properties
Under the old error handler, the reset routine was responsible for
resetting the bus, waiting the timeout (which tul_reset_scsi_bus() does
with a busy wait) and flushing the queue.
In the new scheme, the eh thread takes care of all of this (including a
nice thread based wait).
I think this may all work correctly if you change this call to:
tul_reset_scsi(pHCB, 0);
instead. That should simply reset the bus and not busy wait at all,
which is really what the error handler is expecting.
James
next prev parent reply other threads:[~2004-01-08 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 23:14 Patch for reset in ini9100u [Initio 9100U(W)] Jonathan McDowell
2004-01-08 0:56 ` James Bottomley [this message]
2004-01-18 21:30 ` Jonathan McDowell
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=1073523364.1883.12.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=noodles@earth.li \
/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