From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Sergey Panov <sipan@sipan.org>, Matthew Wilcox <matthew@wil.cx>,
Christoph Hellwig <hch@infradead.org>,
Luben Tuikov <ltuikov@yahoo.com>,
James Bottomley <James.Bottomley@SteelEye.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
Date: Wed, 14 Sep 2005 08:59:53 -0400 [thread overview]
Message-ID: <43281EC9.5070804@adaptec.com> (raw)
In-Reply-To: <43280123.1020700@pobox.com>
On 09/14/05 06:53, Jeff Garzik wrote:
> ...and in this thread, SAS, more than one LLDD -should- be able to make
> use it of.
>
> ServerWorks/Broadcom SAS+SATA hardware, for which I will soon be writing
> a driver, has exactly the same needs as Adaptec SAS+SATA hardware.
Hi Jeff,
Nice of you to finally join us.
I'm sure you've looked at the SAS code. If SW/Broadcom has the same
open transport architecture, as we do, as you say they do, then you
should have no problem generating 4 events (link up/down, BYTES_DMAED,
BROADCAST(x)) to plug right into the SAS Layer, and have it do port
management, discovery, expander configuration, etc, for you.
Please let me know how it goes. I'm very curious.
If there's any concerns with the SAS Layer, I'm willing to help
in anywhich way I can.
Luben
prev parent reply other threads:[~2005-09-14 13:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 19:42 [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Luben Tuikov
2005-09-09 23:35 ` James Bottomley
2005-09-10 4:12 ` Luben Tuikov
2005-09-10 13:08 ` Arjan van de Ven
2005-09-12 13:55 ` Luben Tuikov
2005-09-12 14:13 ` Jörn Engel
2005-09-12 18:46 ` Luben Tuikov
2005-09-12 18:46 ` Luben Tuikov
2005-09-10 14:30 ` Rik van Riel
2005-09-10 20:20 ` Alan Cox
2005-09-11 9:40 ` Christoph Hellwig
2005-09-13 12:41 ` Luben Tuikov
2005-09-11 3:56 ` ak
2005-09-11 13:41 ` James Bottomley
2005-09-12 17:12 ` Luben Tuikov
2005-09-12 17:55 ` Alan Cox
2005-09-12 13:56 ` Luben Tuikov
2005-09-11 9:38 ` Christoph Hellwig
2005-09-12 16:08 ` Matthew Wilcox
2005-09-12 19:07 ` Luben Tuikov
2005-09-12 19:55 ` Matthew Wilcox
2005-09-12 23:51 ` Stefan Richter
2005-09-12 22:00 ` Luben Tuikov
2005-09-13 15:40 ` Matthew Wilcox
2005-09-14 5:56 ` Sergey Panov
2005-09-14 10:37 ` Christoph Hellwig
2005-09-14 10:53 ` Jeff Garzik
2005-09-14 12:59 ` Luben Tuikov [this message]
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=43281EC9.5070804@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.com \
--cc=matthew@wil.cx \
--cc=sipan@sipan.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;
as well as URLs for NNTP newsgroup(s).