From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "christophe barbé" <christophe.barbe@online.fr>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Question: Adaptec AIC7xxx support
Date: Thu, 08 Nov 2001 14:56:56 -0700 [thread overview]
Message-ID: <200111082156.fA8LuuY66000@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Thu, 08 Nov 2001 22:45:58 +0100." <20011108224558.C505@online.fr>
>> >This is a drawback of single driver for multiple cards. Good cards
>> >suffer to enable the driver to support bad ones.
>>=20
>> This has nothing to do with the card the aic7xxx driver is accessing.
>
>Sorry if I upset you.
You didn't upset me. I just wanted to ensure that an inacurate statement
wasn't propogated.
>I was convinced it was to support old hardware.
Yes and no. Although more common in older hardware, there are still
companies that bring new products to market that take *forever* to
wakeup after a bus reset.
>You seems to indicate that it depends more on the attached scsi targets,
>and I believe it but I have never seen this kind of configuration where
>the timeout needs to be 15000 Msec. Is this a so common config to set
>this value as default ?
There are still lots of devices out there that don't work with shorter
timeouts. I don't know that it matters what percentage of people have
these devices so much as allowing them to install/use the OS without
the frustration of trying to figure out how to make their system work.
Other than a bit of wall clock time, the extra delay does not "hurt"
setups that can use a lower timeout.
--
Justin
next prev parent reply other threads:[~2001-11-08 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 17:52 John Gluck
2001-11-08 19:37 ` christophe barbé
2001-11-08 20:06 ` Justin T. Gibbs
2001-11-08 21:45 ` christophe barbé
2001-11-08 21:56 ` Justin T. Gibbs [this message]
2001-11-08 20:05 ` Justin T. Gibbs
2001-11-08 21:08 ` John Gluck
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=200111082156.fA8LuuY66000@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=christophe.barbe@online.fr \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®