From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] piconet..
Date: Sat, 11 Dec 2004 17:44:00 +0100 [thread overview]
Message-ID: <1102783440.19086.28.camel@pegasus> (raw)
In-Reply-To: <002d01c4df96$cc2e2080$6401000a@zool>
Hi Steffen,
> My source code for most of my BTserver can be found at:
> http://www.diku.dk/hjemmesider/studerende/zool/bt/prot.cc
> As you can see in my souce (see the listenL2CAP method), I do almost as you
> told me to do and what l2test.c is doing.
> I use the standard bind, listen and accept methods and spawns of a new
> child, when I get a connection. But I still can't make it work when I have
> more than one client (a piconet). Why is that? can you see a minor flaw in
> my code?
>
> I have made a hciconfig -a with one of my USB dongles (it is a DBT 120
> unit):
>
> hci0: Type: USB
> BD Address: 00:40:05:60:41:0D ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:653 acl:0 sco:0 events:19 errors:0
> TX bytes:314 acl:0 sco:0 commands:18 errors:0
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'fsck-0'
> Class: 0x000100
> Service Classes: Unspecified
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1 (0x1) LMP Subver: 0x1bb
> Manufacturer: Cambridge Silicon Radio (10)
>
> I can only give you this one, because one of my friends have the other two
> dongles. I will though sent the output later tonight, when I get them back.
> :-)
so far so good, but check with "hciconfig hci0 revision" for the
firmware version. This one is too old. It should be HCI 16.4 or newer,
but if this is a DBT-120 Rev. B3 you might have a chance to update it.
> PS: It also seems like that the l2test works with more clients.. I really
> can't see the big difference in my code and l2test.. But mabye it is me..
> ;-)
I think you should use fork(). What is wrong with using poll() or
select() and an event loop.
And btw since you use code from l2test.c etc. you should include the GPL
license statement at the top of your code.
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-12-11 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 10:20 [Bluez-devel] piconet Steffen Larsen
2004-12-11 11:28 ` Marcel Holtmann
2004-12-11 11:00 ` Steffen Larsen
2004-12-11 12:10 ` Marcel Holtmann
2004-12-11 12:10 ` Steffen Larsen
2004-12-11 15:33 ` Steffen Larsen
2004-12-11 16:44 ` Marcel Holtmann [this message]
2004-12-11 16:29 ` Steffen Larsen
2004-12-11 17:37 ` Marcel Holtmann
2004-12-11 17:50 ` Steffen Larsen
2004-12-13 9:48 ` Steffen Larsen
2004-12-13 9:54 ` Steffen Larsen
2004-12-13 11:05 ` 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=1102783440.19086.28.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