Re: [Bluez-devel] Regarding a2recv

["Henryk Plötz" <henryk@ploetzli.ch>]

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

Moin,

Am Mon, 09 May 2005 02:01:36 +0200 schrieb Marcel Holtmann:

> I suspect that it is waiting for a role switch to happen.

Either that isn't it or I'm doing it wrong. There should be two
principal ways to archieve this, right? 

a) hciconfig hci0 lm master
If I do this I don't get a complete connection at all. hcidump shows
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:08:F4:35:05:3C role 0x00
    Role: Master
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Role Change (0x12) plen 8
> HCI Event: Connect Complete (0x03) plen 11
but nothing shows up on a2recv. 

b) (I got this from the bthid code)
getsockopt(fd, SOL_L2CAP, L2CAP_LM, &opt, &len)
opt |= L2CAP_LM_MASTER;
setsockopt(fd, SOL_L2CAP, L2CAP_LM, &opt, sizeof(opt))

I'm not sure on which fd I should apply this. If I do it on the streamfd
right after it has been established the behaviour is just as normal
(e.g. 6 second hang, then disconnect).

If I do it with the listening socket right in the beginning I get the
same as with hciconfig above. (I swear I got a "Role change not allowed"
message from kdebluetoothd somewhere in between, but I can't reproduce
that.)

-- 
Henryk Plötz
Grüße aus Berlin
~~~~~~~ Un-CDs, nein danke! http://www.heise.de/ct/cd-register/ ~~~~~~~
~ Help Microsoft fight software piracy: Give Linux to a friend today! ~

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]