Date: Wed, 12 Apr 2006 20:48:33 +0100 (BST) From: Iain Hibbert <plunky@rya-online.net> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: headset/sco support in freebsd Message-ID: <1144871314.024068.10495.nullmailer@galant.ukfsn.org> In-Reply-To: <443D3A30.2020109@savvis.net> References: <20060314181140.GB6870@lbl.pl> <44170EDA.5000406@savvis.net> <1144841743.207833.9946.nullmailer@galant.ukfsn.org> <443D3A30.2020109@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Apr 2006, Maksim Yevmenkin wrote: > imo, none of the SOCK_xxx types describes sco exactly. to me its either > SOCK_DGRAM/SOCK_SEQPACKET (more preferred) or SOCK_STREAM (less preferred). [..] > in other words sco "protocol" has (some) SOCK_SEQPACKET properties vs. sco > "protocol" is/can be used to transfer SOCK_STREAM type of data. Thats kind of what I thought too only I was leaning the other way until I saw what the other guys did. Well I am hoping that the sockets part of it will be mostly irrelevant since I am aiming to create a kernel audio device that can be set on top of the SCO code, and in fact after already working on L2CAP (SEQPACKET) and RFCOMM (STREAM) I think SEQPACKET is an easier concept to program, and so would leave the packetising to the audio driver, which may help keep latency down.. regards, iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1144871314.024068.10495.nullmailer>