Re: [Bluez-users] Byte order for baddr-to-string

Hi Mats,

I observe that the bluez-libs functions 

  int ba2str(const bdaddr_t *, char *);

  char * batostr(const bdaddr_t *);

deliver strings with different byte order. Is it just
me making a slip of mind regarding netorder or endianness,
or is there a deeper reason that I fail to comprehend?
I observe the same thing on i386 architecture as well
as on cris architecture.

it is part of the specification. The user visible presentation is
different from the wire one.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users