whitespace
Maksim Yevmenkin
maksim.yevmenkin at savvis.net
Tue Mar 7 17:03:08 PST 2006
Iain Hibbert wrote:
> On Tue, 7 Mar 2006, Maksim Yevmenkin wrote:
>
>>then add appropriate #define's for shortcut access to the union fields. i can
>>then change freebsd code to use single 'struct sockaddr_bt' as well.
>
> Hm, this could work though there are a couple of differences still, in
> that I have used the bdaddr for HCI socket addressing where you use the
> text name of the node (I convert name->bdaddr via an ioctl() if necessary)
another union inside _hci part?
> Also, it is possible in my implementation to specify an alternate PSM for
> rfcomm sockets (as I read the spec, this is allowed..)
sure its allowed, but why would you want to do this? there is no way for
the remote device to know that the local device runs rfcomm on some
other (than 3) psm. in the same way you could run sdp on any psm. it
will work, as long as you control both sides - server and client.
changing "well known" psm is a sure way to get into all sorts of
interoperability problems.
thanks,
max
More information about the freebsd-bluetooth
mailing list