All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: mats.andersson@blue2net.com,
	BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Byte order for baddr-to-string
Date: Thu, 30 Aug 2007 17:17:35 +0200	[thread overview]
Message-ID: <1188487055.13373.31.camel@violet> (raw)
In-Reply-To: <1188486698.4817.60.camel@Blue2net-mats.bellman.mea>

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

      reply	other threads:[~2007-08-30 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 15:11 [Bluez-users] Byte order for baddr-to-string Mats Erik Andersson
2007-08-30 15:17 ` Marcel Holtmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1188487055.13373.31.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=mats.andersson@blue2net.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.