Darren J Moffat wrote:
> Alan DuBoff wrote:
>> On Wednesday 29 November 2006 08:25 am, Garrett D'Amore wrote:
>>> Darren, please have a look at NetBSD's bluetooth stack, which was
>>> written by Iain Hibbert.  This stack is provided under a friendly BSD
>>> license, and was funded by Tadpole.  We may be able to offer some help
>>> in this area, as well.
>>
>> That would be nice if we could get that ported to OpenSolaris.
>
> Is there something specific in the NetBSD stack you want Alan or do
> you want a Bluetooth stack ?
>
> A 1:1 port isn't going to be possible, but what we might be able to do
> is leverage core parts of some other open source bluetooth stack. 
> There will be some critical differences in how it integrates into
> OpenSolaris though because of things like devfsadm etc.
>


Actually, the core protocol bits could at _minimum_ serve as a
reference, and you can wholesale lift certain routines as you find them
useful.  I think _no_ free BT stack is going to be trivial to port to
Solaris, largely because Solaris has STREAMs and everything else uses
some other method.   But being able to pick up various routines via
cut-paste may make implementation go faster, and not having to worry
about GPL issues makes NetBSD more attractive, I think.

The NetBSD stack supports HID, audio, comms, networking (PPP over your
3G phone :-), and hands free profiles.

The devfsadm and configuration parts of BT are one area that I consider
a weakness in the NetBSD arena, but I think we (Solaris) can do a lot
better.  (NetBSD itself more or less lacks good support for dynamic
configuration, whereas Solaris has had it from the get-go.)

I'd be interested in working on this project, but I think I don't have
the time at the moment.  That could change in little while though.

-- 
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134  Fax: 951 325-2191

_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to