From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btohs,btohl, ...
Date: Wed, 09 Feb 2005 14:57:10 +0100 [thread overview]
Message-ID: <1107957430.13863.34.camel@pegasus> (raw)
In-Reply-To: <20050209143858.1e0350c3@CleverSophie>
Hi Bjoern,
> sorry for my signing. I read that sometimes a different order is used within a byte as well and not only between bytes.
I don't know of any architecture that stores the bits of its bytes in a
different order and where this is visible to for the user. However such
a platform might exists.
> Okay that makes it easier.
You mean big endian communicates with little endian or vice versa?
> But if this is not the case:
> When I send a 32bit integer for example, do I have to worry about the order of the bytes when I send or receive them?
If you have a byte stream (a character array) then you don't need to
worry, because they are stored in a endianless format (bytewise). If you
use datatypes like uint16_t and uint32_t and send them to the stream or
copy them into an array then you should convert them to the same endian
encoding.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-09 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 13:07 [Bluez-devel] btohs,btohl, # Björn Specht #
2005-02-09 13:19 ` Marcel Holtmann
2005-02-09 13:38 ` # Björn Specht #
2005-02-09 13:57 ` Marcel Holtmann [this message]
2005-02-09 14:00 ` # Björn Specht #
2005-02-09 15:07 ` [Bluez-devel] omtu, imtu # Björn Specht #
2005-02-09 15:18 ` Marcel Holtmann
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=1107957430.13863.34.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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.