public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Roscic <simon.roscic@chello.at>
To: linux-kernel@vger.kernel.org
Subject: [Kernel 2.5] Qlogic 2x00 driver
Date: Tue, 15 Oct 2002 21:20:13 +0200	[thread overview]
Message-ID: <200210152120.13666.simon.roscic@chello.at> (raw)

hi,

as the feature freeze of 2.5 comes close, i want to ask if the driver for
the qlogic sanblade 2200/2300 series of hba's will be included in 2.5 ...
are there any plan's to do so ?   has it been discussed before ?

i ask because i use those hba's together with ibm's fastt500 storage system,
and it will be nice to have this driver in the default kernel ...

i use version 5.36.3 of the qlogic 2x00 driver in production
(vanilla kernel 2.4.17 + qlogic 2x00 driver v5.36.3) since may 2002
and i never had any problems with this driver ...
(2 lotus domino servers and 1 fileserver all 3 are attached to the ibm fastt500
storage system using qlogic sanblade 2200 cards)

i don't know how many people use those qlogic card's, i got them together
with the fastt500 storage system, ...

the current driver is avaiable here (it's GPL't):
http://www.qlogic.com/support/os_detail.asp?productid=112&osid=26

the qlogic 2x00 driver is also in andrea arcangelis "-aa" patches, so possibly
he knows better if it would be useful to integrate those drivers into 2.5 or
not, ...

thanks for your time,
please CC me, i'm currently not subscribed to lkml,
simon.


             reply	other threads:[~2002-10-15 19:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 19:20 Simon Roscic [this message]
2002-10-15 19:31 ` [Kernel 2.5] Qlogic 2x00 driver Arjan van de Ven
2002-10-15 19:53   ` Simon Roscic
2002-10-16  2:51     ` Michael Clark
2002-10-16  3:56       ` GrandMasterLee
2002-10-16  4:30         ` Michael Clark
2002-10-16  4:35           ` J Sloan
2002-10-16  4:43             ` GrandMasterLee
2002-10-16  6:03               ` Michael Clark
2002-10-16  6:31                 ` GrandMasterLee
2002-10-16  6:40                   ` Michael Clark
2002-10-16  6:48                     ` GrandMasterLee
2002-10-16  6:59                       ` Michael Clark
2002-10-16  4:58             ` GrandMasterLee
2002-10-16  5:28             ` Michael Clark
2002-10-16  5:40               ` Andreas Dilger
2002-10-17  1:59                 ` Andrew Vasquez
2002-10-17  2:44                   ` GrandMasterLee
2002-10-17  3:11                     ` Andrew Vasquez
2002-10-17  3:42                       ` GrandMasterLee
2002-10-17  9:40                       ` Michael Clark
2002-10-18  6:45                         ` GrandMasterLee
2002-10-16 16:28       ` Simon Roscic
2002-10-16 16:49         ` Michael Clark
2002-10-17  3:12           ` GrandMasterLee
2002-10-17  3:54             ` Michael Clark
2002-10-17  4:08               ` GrandMasterLee
2002-10-17  5:03                 ` Michael Clark
2002-10-16  5:02 ` GrandMasterLee
2002-10-16 16:38   ` Simon Roscic
2002-10-17  3:08     ` GrandMasterLee
2002-10-17 17:47       ` Simon Roscic
2002-10-18  6:42         ` GrandMasterLee
2002-10-18 15:11           ` Simon Roscic
  -- strict thread matches above, loose matches on Subject: below --
2002-10-19  2:17 rwhron

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=200210152120.13666.simon.roscic@chello.at \
    --to=simon.roscic@chello.at \
    --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