All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bradley Grove <bgrove@attotech.com>
To: James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, Jason Seba <jseba@attotech.com>
Subject: ATTO 6G SAS/SATA HBA Driver
Date: Tue, 03 Sep 2013 13:11:49 -0400	[thread overview]
Message-ID: <52261855.7050503@attotech.com> (raw)


James,

Now that we are finishing up development for our esas2r driver, we are 
planning to start work on a kernel driver for our PM8001 based 6G 
SAS/SATA HBA product.  We have some questions about the best way to proceed.

While we haven't done thorough testing, our hardware appears to work 
with the existing PM8001 kernel driver.   The problem is that the 
existing kernel driver doesn't support all the features of the hardware 
or match the feature set of the current closed source driver.   For 
example, our closed source driver supports SES emulation over I2C and 
SGPIO.  Our closed source driver also has custom PHY settings to support 
longer cable lengths.   We also have a set of propriety management tools 
we'd like to work with the open source driver, though it looks like the 
PM8001's sysfs interface provides most of the functionality we need.

What are our options for supporting these features?  I see that Adaptec 
had an out-of-tree driver for their PM8001 card that supports additional 
features.   We'd prefer to have a kernel driver that fully supports our 
hardware, either based on the existing PM8001 driver or our closed 
source code base.   Is that possible?

-- 
Bradley Grove
System Software Engineer
ATTO Technology, Inc.
Phone:  +1.716.691.1999 ext. 144
Fax +1.716.691.9353
"Powering the World's Networks & Storage"

             reply	other threads:[~2013-09-03 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 17:11 Bradley Grove [this message]
2013-09-03 19:30 ` ATTO 6G SAS/SATA HBA Driver James Bottomley

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=52261855.7050503@attotech.com \
    --to=bgrove@attotech.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jseba@attotech.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.