public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@myrealbox.com>
To: linux-kernel@vger.kernel.org
Cc: Willy Tarreau <willy@w.ods.org>
Subject: Re: Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2)
Date: Sat, 24 May 2003 16:06:33 -0400	[thread overview]
Message-ID: <3ECFD0C9.7020002@myrealbox.com> (raw)
In-Reply-To: E19JXTg-0000HO-00@neptune.local

Pascal Schmidt wrote:
> On Fri, 23 May 2003 22:30:17 +0200, Willy Tarreau wrote in lkml:
> 
> 
>>By this time, there will be more and more people leaving vanilla kernel for
>>their machines, and using them only as a base to apply -aa, -ac, -jam, -wolk,
>>-** + sf.net/* + who_knows_what, and I find it a shame.
> 
> 
> I think you overestimate the number of aic7xxx users. It's not like
> 99% of all 2.4 users need the driver.
> 

I think you're smoking crack, I'd say that there are way more than 1% of 
the 2.4 users w/ an AIC-7XXX chipset based controller.  I don't know how 
things are like in Germany, but around here, Adaptec is usually thought 
to be the mainstream choice in SCSI solutions for professional 
workstations and low-to-mid range servers [I Am Not A Product Market 
Analyst, so this is just my personal opinion based on my experiences in 
the VAR/Retail sector...  YMMV].  Most of the popular OEM's offer some 
sort of SCSI option based on an AIC-7XXX series chipset for most of 
their non "home-use-only" lines.  I can't even count how many 
motherboard manufactures have embedded the AIC-7XXX series chip into 
their motherboard to provide integrated SCSI solutions.  Moreover, most 
of what Adaptec produces in their current core SCSI brand line 
(excepting DPT, etc) is based on some version of the AIC-7XXX chip.  I 
can damn well say for sure there are more AIC-7XXX users then there are 
Fusion users and, as was pointed out, that code has gone through much 
more invasive changes to bring it up to speed.

I think the bottom line is that those of us in Adaptec-userland would 
very much appreciate a *working*, current driver in the next kernel 
release.  AFAICT, the old code base that was reverted to still has some 
annoying "quirks", and frankly doesn't perform as well as the current 
driver [at least for me].  So, invasive or not, I think we ought to be 
"testing the code" of a driver release written by a person who is well 
qualified to know the ins and outs of the hardware he is writing the 
code for.  Obviously Justin has access to a multitude of Adaptec 
hardware and I am quite satisfied that he has sufficiently tested his 
modifications to the driver.  Waiting until 2.4.22, let alone 2.4.21, is 
actually released just seems too far down the road to be sane.

Just my $0.02 on this...

Cheers,
Nicholas



  reply	other threads:[~2003-05-24 19:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030523085010$1ac2@gated-at.bofh.it>
     [not found] ` <20030523180021$109a@gated-at.bofh.it>
     [not found]   ` <20030523203017$0e66@gated-at.bofh.it>
2003-05-24 11:46     ` Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2) Pascal Schmidt
2003-05-24 20:06       ` Nicholas Wourms [this message]
2003-05-28 23:11       ` Bill Davidsen
2003-05-27  9:12 Eric Valette
  -- strict thread matches above, loose matches on Subject: below --
2003-05-26 21:53 john
2003-05-23 23:29 James Bottomley
2003-05-24  6:43 ` Willy Tarreau
2003-05-24 14:36   ` James Bottomley
2003-05-24 14:51     ` Justin T. Gibbs
2003-05-24 15:55       ` James Bottomley
2003-05-28 23:08     ` Bill Davidsen
2003-05-26  4:21   ` David S. Miller
2003-05-26  4:25   ` David S. Miller
2003-05-26  8:47     ` Marc-Christian Petersen
2003-05-26 17:58     ` Marcelo Tosatti
2003-05-26 18:42     ` Marcelo Tosatti
2003-05-26 21:29       ` Willy Tarreau
2003-05-26 21:35         ` Marcelo Tosatti
2003-05-27  4:21           ` Willy Tarreau
2003-05-26 22:16       ` Carl-Daniel Hailfinger
2003-05-26 22:18         ` Marc-Christian Petersen
2003-05-26 22:33           ` Carl-Daniel Hailfinger
2003-05-27  0:35     ` Alan Cox
2003-05-27  4:39       ` Willy Tarreau
2003-05-27  4:47         ` Marcelo Tosatti
2003-05-27  5:00           ` Willy Tarreau
2003-05-27  8:38         ` Oliver Pitzeier
2003-05-27  8:44           ` Marc-Christian Petersen
2003-05-27  9:44             ` Oliver Pitzeier
2003-05-27 20:01           ` Marcelo Tosatti
2003-06-23  7:57             ` Oliver Pitzeier
2003-05-11 19:08 Linux 2.4.21-rc2 Sven Krohlas
2003-05-22 15:19 ` Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2) Oliver Pitzeier
2003-05-22 15:31   ` Marc-Christian Petersen
2003-05-22 21:33     ` Scott McDermott
2003-05-23  8:45       ` Oliver Pitzeier
2003-05-23 17:52         ` Marcelo Tosatti
2003-05-23 20:19           ` Willy Tarreau
2003-05-23 22:58         ` Scott McDermott
2003-05-26 18:51           ` Marcelo Tosatti
2003-05-23  7:17     ` Sven Krohlas
2003-05-26 12:54       ` Matthias Andree
2003-05-23  7:14   ` Sven Krohlas
2003-05-23  8:48     ` Oliver Pitzeier
2003-05-23  9:26       ` Sven Krohlas
2003-05-23  9:32         ` Oliver Pitzeier
2003-05-23 11:33           ` Stephan von Krawczynski
2003-05-24  0:18         ` J.A. Magallon
2003-05-23 15:20       ` Disconnect

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=3ECFD0C9.7020002@myrealbox.com \
    --to=nwourms@myrealbox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.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