From: Marcel Holtmann <marcel@holtmann.org>
To: radoa <cat@pobox.sk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: hci event bug for Nokia 7650
Date: Fri, 29 Oct 2004 21:03:58 +0200 [thread overview]
Message-ID: <1099076638.6912.5.camel@pegasus> (raw)
In-Reply-To: <loom.20041029T203002-259@post.gmane.org>
Hi Radoa,
> Kernel version is 2.6.9 with Bluetooth kernel patch 2.6.9-mh2.
> Here is code (dst address is changed):
>
> int test_connect()
> {
> struct sockaddr_l2 sa;
> int fd, ret;
> bdaddr_t *dst = {{0, 1, 2, 3, 4, 5}};
>
> // success
> fd = socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_L2CAP);
>
> sa.l2_family = AF_BLUETOOTH;
> sa.l2_psm = htobs(SDP_PSM); // 0x0001
> sa.l2_bdaddr = *dst;
>
> // this will fail
> ret = connect(fd, (struct sockaddr *)&sa, sizeof(sa));
>
> return ret;
> }
actually I don't understand how that should ever work. Do you looked at
the example code? We don't do these nasty BD_ADDR tricks. You should
better use this one:
str2ba("aa:bb:cc:dd:ee:ff", &sa.l2_bdaddr);
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-10-29 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 17:50 [Bluez-devel] hci event bug for Nokia 7650 radoa
2004-10-29 18:11 ` Marcel Holtmann
2004-10-29 18:47 ` [Bluez-devel] " radoa
2004-10-29 19:03 ` 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=1099076638.6912.5.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=cat@pobox.sk \
/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