All of lore.kernel.org
 help / color / mirror / Atom feed
From: "# Björn Specht #" <bspecht@gmx.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btohs,btohl, ...
Date: Wed, 9 Feb 2005 14:38:58 +0100	[thread overview]
Message-ID: <20050209143858.1e0350c3@CleverSophie> (raw)
In-Reply-To: <1107955171.13863.26.camel@pegasus>

Hi Marcel,

sorry for my signing. I read that sometimes a different order is used withi=
n a byte as well and not only between bytes.=20
Okay that makes it easier.
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?=20

Bj=F6rn


On Wed, 09 Feb 2005 14:19:31 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Bjoern,
>=20
> if you sign emails that go to a mailing list. Make sure that your key is
> available on a public keyserver. Yours is not.
>=20
> > I implemented a client server over bluetooth and I was wondering if I n=
eed the Little Endian, Big Endien conversion functions btohs,btohl,htobs,ht=
obl?
>=20
> if both sides are of the same endianess then not, but it is a good
> programming style to always use them.
>=20
> > Do I need to convert every single byte? which is received or sent over =
my sock_stream socket?
> > If yes, should it look like this for the receiving case: btohs(buf[0]).=
... an so on for every byte?
>=20
> For what do you wanna swap a byte and with what? There is nothing to
> swap. Think about it ;)
>=20
> Regards
>=20
> Marcel
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> 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=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>=20


-------------------------------------------------------
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

  reply	other threads:[~2005-02-09 13:38 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 # [this message]
2005-02-09 13:57     ` Marcel Holtmann
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=20050209143858.1e0350c3@CleverSophie \
    --to=bspecht@gmx.net \
    --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.