From: Brian King <brking@us.ibm.com>
To: Robert Tarte <robt@PacificCodeWorks.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Alexis Bruemmer <alexisb@us.ibm.com>,
Mike Anderson <andmike@us.ibm.com>,
"Tarte, Robert" <Robert_Tarte@adaptec.com>
Subject: Re: aic94xx status
Date: Thu, 20 Jul 2006 09:39:28 -0500 [thread overview]
Message-ID: <44BF95A0.1090703@us.ibm.com> (raw)
In-Reply-To: <16C8363E16D7234AB844FDB52D4AEA650C2DB7@ntserv.PacificCodeWorks.local>
Robert Tarte wrote:
>> 1) SATA support. We at least need this stubbed out so seeing a SATA
>> device won't cause nasty things to happen (IBM is working on this).
>> Ideally, we need to integrate this driver with Brian King's SATA/SAS
>> code, but no-one who has this board has a sata device and vice versa.
>
> [Tarte, Robert] I'm not sure what Brian King's SATA/SA code is, but I do
> have boards that use the razor chip and I have SATA devices.
The patch referred to here is a patch to libata that adds a set of APIs
that allows a SAS HBA to hook into libata to control SATA devices. It
was written so that I could get ipr to hook into libata, and the hope
is that it could be used by other SAS drivers as well. Unfortunately,
no other SAS drivers that support SATA passthrough have really tried
using it yet.
http://marc.theaimsgroup.com/?l=linux-ide&m=115279779219927&w=2
Brian
next prev parent reply other threads:[~2006-07-20 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 8:32 aic94xx status Robert Tarte
2006-07-20 14:39 ` Brian King [this message]
2006-07-20 18:39 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2006-07-08 16:27 James Bottomley
2006-07-10 16:09 ` Mike Anderson
2006-07-10 16:27 ` James Bottomley
2006-07-11 5:07 ` Mike Anderson
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=44BF95A0.1090703@us.ibm.com \
--to=brking@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Robert_Tarte@adaptec.com \
--cc=alexisb@us.ibm.com \
--cc=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=robt@PacificCodeWorks.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