Looks like there is either a problem with my card or
with the bluecard module? Given that the card works
fine with BlueZ I don't think it's the card.
It is: Anycom Model CF-2000
FCC ID OXTLSE039
cardctl ident reports:
product info: "WSS", "LSE039"
manfid: 0x0264, 0x008
function: 6 (network)
Socket CF card works with the same kernel package, so
the problem is probably in the bluecard module alone.
Logged In: YES
user_id=610275
Card initialises OK. btctl reports that the interface is up and
looks good. "btctl inquiry" discovers devices fine. Any attempt
to browse services or connect to a device gives "Could not
connect to SDP server"
Logged In: YES
user_id=401984
Confirm this happens for me as well. Trying to bypass SDP also fails:
root@zaurus ~ # btctl --nosdp connect 00:80:37:2e:36:20 1
Connecting to host 00:80:37:2e:36:20 ...
Connecting to channel 1 ...
Unable to connect to remote side
root@zaurus ~ #
additionally, when trying to pair:
root@zaurus ~ # btctl pair 00:80:37:2e:36:20
unable to create connection
At which point the zaurus locks up solid, and requires a manual reset.
I'm happy to help with testing code on ARM.