Date: Tue, 14 Mar 2006 20:21:30 +0000 (GMT) From: Iain Hibbert <plunky@rya-online.net> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: config files Message-ID: <1142367690.557055.3307.nullmailer@galant.ukfsn.org> In-Reply-To: <4417191C.8030501@savvis.net> References: <1141918855.418446.1437.nullmailer@galant.ukfsn.org> <44107678.1080206@savvis.net> <1142195365.759631.5369.nullmailer@galant.ukfsn.org> <44160BE9.9020306@savvis.net> <1142325762.357474.659.nullmailer@galant.ukfsn.org> <44170ADD.3080706@savvis.net> <1142364014.786820.1535.nullmailer@galant.ukfsn.org> <4417191C.8030501@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 14 Mar 2006, Maksim Yevmenkin wrote:
> well, not in freebsd. just like in sockaddr_in port/ip have to passed (to
> kernel) in network byte order, psm in sockaddr_l2cap has to be passed (to
> kernel) in le16 byte order.
Its a confusing issue I agree - my decision was that bdaddr is an opaque
type and I couldnt see any utility in swapping it around and getting
confused (I think Linux does this with baswap() macro), but that psm was a
value and should be represented as such.
in inet(3) I see the following comment
All Internet addresses are returned in network order (bytes ordered from
left to right). All network numbers and local address parts are returned
as machine format integer values.
which matches what I did, so I'm happy :)
iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1142367690.557055.3307.nullmailer>