public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] baswap neccesity
Date: Mon, 10 Jan 2005 21:27:02 +0100	[thread overview]
Message-ID: <1105388822.8652.53.camel@pegasus> (raw)
In-Reply-To: <cruhvs$fj5$1@sea.gmane.org>

Hi,

> I'm reading rctest.c:
> In do_connect function, a call to bswap is used just before the connect 
> call:
> 	baswap(&rem_addr.rc_bdaddr, strtoba(svr));
> 
> In the server, baswap is again called just after the accept call
> 
> Why is it neccesary? Why does the server listening at the other side 
> expect addresses in such byte ordering?

this is part of the specification. The textual representation and the
over-air BD_ADDR is swapped.

However the code above has a memory leak. Where do you found it?

> mmm, again thank you for your time (sometimes I feel like trying to slow 
> down a bit your work would enable me to get up to date, but it's 
> useless, the rate of events is dramatic and you always reemerge... ;-) )

Sorry for that ;)

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2005-01-10 20:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 18:36 [Bluez-devel] baswap neccesity soraberri
2005-01-10 18:47 ` [SPAM?]: " Till Harbaum
2005-01-10 20:27 ` Marcel Holtmann [this message]
2005-01-11  8:52   ` [Bluez-devel] " soraberri
2005-01-11  9:59     ` 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=1105388822.8652.53.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox