lkml.org 
[lkml]   [2007]   [Sep]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Broadcom 8603 SAS/SATA driver, rough draft
James Bottomley wrote:
> On Sun, 2007-09-23 at 19:43 -0400, Jeff Garzik wrote:
>> James Bottomley wrote:
>>> On Sun, 2007-09-23 at 00:04 -0400, Jeff Garzik wrote:
>>>> Rather than sitting on this for far too long, I wanted to go ahead and
>>>> get this out there. I heard some chips might be trickling out into
>>>> public hands.
>>> The first thing to note is about the specs and the pre-production
>>> hardware: the Linux Foundation has mechanism to get both into the hands
>>> of interested developers; if you can point me to contacts, I can at
>>> least get the NDA documentation programme ball rolling.
>> Well, are there interested, motivated, skilled developers with time? :)
>>
>> Otherwise it's a moot point.
>
> We have GregKH's minions ... this would be a good project for them.

> Same answer ... GregKH has a legion ... lets use it.

This is a good project for somebody who knows how SAS behaves on the
wire, which is a rather limited group.

I'm willing to help anyone who proactively moves in this direction, but
they need to be proactive about it... I am the person who will have to
make introductions at Broadcom, and convince Broadcom that new Person is
a highly capable SAS software engineer.

Telling bcm "I don't know this guy, its doubtful he knows SAS, but we
want to make him the primary engineer anyway" is not a very winning tale :)

> SMP and STP, by the way, are simple frame in, frame out. If it
> identifies the initiator and target protocols and allows us to send
> frames, we can probably transmit both protocols.
[...]
> That's going to be a bit of a bit oops ...
[...]
> well, I suppose it was designed for simple direct connection ...

That's the way it's looking. There are a few avenues for exposing
IDENTIFY and OPEN frames and related details, but no obvious "any frame,
no problem" method like with the Marvell chip.

IMO it's also indicative that Marvell's chip uses a single set of
command and response queues, whereas Broadcom has command/response
queues for each "port" (bcm's term).

Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-09-24 02:17    [W:0.040 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site