From: Douglas Gilbert <dougg@torque.net>
To: Michael Heinz <mheinz@infiniconsys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Resources for SCSI, SRP, Infiniband?
Date: Mon, 06 Aug 2001 23:51:30 -0400 [thread overview]
Message-ID: <3B6F65C2.64BC3C1A@torque.net> (raw)
Michael Heinz <mheinz@infiniconsys.com> wrote:
> I'm tasked with developing a new SCSI driver for 2.4;
> but I'm running into issues that (a) SCSI drivers
> are different from other Linux device drivers and
> (b) none of the SCSI driver docs/how-tos seem to have
> been updated since 2.0.x.
Strange, I'm pretty certain the linux documentation
project now includes my document:
http://www.linuxdoc.org/HOWTO/SCSI-2.4-HOWTO
and has for the last 6 months.
> I'm making progress, but could someone direct me to
> a list of do's and don't's for SCSI drivers in 2.4?
Have you looked at Eric Youngdales site:
http://www.andante.org/scsi.html ?
Alan Cox wrote an article about developing a SCSI driver
(but its a little out of date). Then there are the
maintainers of the existings scsi adapter drivers
who may lend you a hand. Best to address your general
scsi queries to the linux-scsi@vger.kernel.org
> Also, anybody else looking at developing IB and or SRP?
I went to an IB talk at the OLS and it seems that most
players don't want to say much; so much for open
software.
Doug Gilbert
next reply other threads:[~2001-08-07 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 3:51 Douglas Gilbert [this message]
2001-08-07 5:29 ` Resources for SCSI, SRP, Infiniband? Matthew Jacob
[not found] <mailman.997195920.28446.linux-kernel2news@redhat.com>
2001-08-07 18:49 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2001-08-07 14:06 Heinz, Michael
2001-08-06 20:58 Heinz, Michael
[not found] <mailman.997107541.5496.linux-kernel2news@redhat.com>
2001-08-06 20:13 ` Pete Zaitcev
2001-08-06 14:17 Michael Heinz
2001-08-07 14:49 ` Oliver Xymoron
2001-08-07 15:02 ` Michael Heinz
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=3B6F65C2.64BC3C1A@torque.net \
--to=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mheinz@infiniconsys.com \
/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