From: Peter Samuelson <peter@cadcamlab.org>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: aic7xxx (and sym53c8xx) plans
Date: Mon, 19 Feb 2001 14:27:14 -0600 (CST) [thread overview]
Message-ID: <14993.33186.622147.313411@wire.cadcamlab.org> (raw)
In-Reply-To: <20010217180547.B28785@cadcamlab.org> <200102181714.f1IHE8O94912@aslan.scsiguy.com>
[Justin Gibbs]
> I've verified the driver's functionality on 25 different cards thus
> far covering the full range of chips from aic7770->aic7899.
That's very good to hear. I know the temptation of only testing on new
hardware; that's why I was concerned.
> Lots of people here at Adaptec look at me funny when I pull a PC from
> the scrap-heap, or pull an old, discontinued card from an unused
> marketing display for use in my lab
Heh. (:
BTW, is there really enough common ground between the whole series of
AIC chips to justify a single huge driver? I know they ship three
separate NT drivers to cover this range..
Peter
next prev parent reply other threads:[~2001-02-19 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 17:19 Nathan Black
2001-02-18 0:05 ` Peter Samuelson
2001-02-18 17:14 ` Justin T. Gibbs
2001-02-19 20:27 ` Peter Samuelson [this message]
2001-02-19 19:32 ` Gérard Roudier
2001-02-19 21:39 ` Matthew Jacob
2001-02-19 21:58 ` Justin T. Gibbs
-- strict thread matches above, loose matches on Subject: below --
2001-02-19 15:28 Nathan Black
2001-02-15 17:38 Matt Liotta
2001-02-15 17:47 ` Justin T. Gibbs
2001-02-15 20:20 ` J . A . Magallon
2001-02-15 20:28 ` Chip Salzenberg
2001-02-15 23:42 ` J . A . Magallon
2001-02-15 17:30 Matt Liotta
2001-02-15 17:35 ` Justin T. Gibbs
2001-02-15 2:03 aic7xxx plans Wakko Warner
2001-02-15 2:06 ` Matthew Jacob
2001-02-15 2:20 ` aic7xxx (and sym53c8xx) plans Chip Salzenberg
2001-02-15 2:28 ` Matthew Jacob
2001-02-15 11:45 ` Alan Cox
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=14993.33186.622147.313411@wire.cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=gibbs@scsiguy.com \
--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®