On Tue, Jun 16, 2009 at 10:17 PM, Jason King<[email protected]> wrote:
> On Tue, Jun 16, 2009 at 2:08 PM, Cyril Plisko<[email protected]> 
> wrote:
>> On Tue, Jun 16, 2009 at 10:05 PM, Jason King<[email protected]> wrote:
>>> On Tue, Jun 16, 2009 at 1:54 PM, Mark Martin<[email protected]> wrote:
>>>> Now that the cat is out of the bag on the ARM port, it's time to see what
>>>> hardware platforms we can try running on.  Is anyone working on, or
>>>> interested in working on, drivers for some of the prevalent ARM platforms?
>>>>  I'm noting that 88F6281 fairly commonly found and inexpensive (QNAP,
>>>> SheevaPlug, etc).  QNAP has expressed interest in supporting a porting
>>>> project, so now would be a good time to think about making sure we have 
>>>> core
>>>> driver support.  It'd be nice if we knew what might be in the pipeline from
>>>> this Sun/NEC collaboration (hint hint).
>>>
>>> The question is, are the companies involved willing to release the
>>> needed specs (or are they already available online)?  While we could
>>> probably port any equivalent drivers from one of the BSD variants
>>> (where those drivers exist), having the specs would be better.
>>
>> http://www.marvell.com/files/products/embedded_processors/kirkwood/HW_88F6281_OpenSource.pdf
>>
>> 140 pages worth of hardware manual. Not sure whether it is enough or
>> not though. I do not have the actual hardware...
>
> It looks like that'd be more useful for someone designing a MB to put
> the chip in than those looking to provide OS support.  It doesn't seem
> to have any details on (for example): programming the two gige
> interfaces (I'd be looking for things like register descriptions,
> descriptor layouts, etc.), the crypto engine, sata controller, etc.
>

http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf

Any better ?

-- 
Regards,
        Cyril
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to