All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Aijaz Baig <aijazbaig1@gmail.com>, linux-scsi@vger.kernel.org
Subject: Re: Venturing into HBA driver development
Date: Sun, 26 Apr 2020 17:04:39 -0700	[thread overview]
Message-ID: <1587945879.3423.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHB2L+cDZCMAwQhVxU99Dwa7Fj90Wwn7qZ9e=78MCqQdwrEjGQ@mail.gmail.com>

On Mon, 2020-04-27 at 05:24 +0530, Aijaz Baig wrote:
> I'm a mid level developer with acceptable knowledge of OS internals
> and some driver development but up until now, I've worked mostly on
> the networking side of things
> 
> most searches online are leading me to open solaris which seems to be
> the only guide available online for writing HBA drivers
> 
> Is there anything else (Besides reading the source), like a guide or
> something, that I can read to help me get up to speed with it.

This is a pretty good one

https://lwn.net/Kernel/LDD3/

And if you like it, you could buy the book.

> Do I really need to know SAN to become acceptably good. How much SCSI
> (and other protocol(s)) knowledge is needed?

It depends *what* driver you want to write.  Obviously you have to
understand the protocol of both the host bus adapter and usually also
any devices attached to it, but the HBA protocol is usually highly
manufacturer dependent, it's only the device protocol that you'll find
in standards.

James


  reply	other threads:[~2020-04-27  0:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 23:54 Venturing into HBA driver development Aijaz Baig
2020-04-27  0:04 ` James Bottomley [this message]
2020-04-27  0:26   ` Aijaz Baig

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=1587945879.3423.5.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=aijazbaig1@gmail.com \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.