Re: Bluetooth

[Pawel Kot]

Hi Marcel,

On 18 Feb 2003, Marcel Holtmann wrote:

> > If I understand you correctly, calling device_open() with
> > GN_CT_Bluetooth
> > instead of GN_CT_Serial from fbus.c and atbus.c (that would call
> > bluetooth_open() instead of serial_open()) should be enough to
> > use the socket interface. Unfortunately it does not work. What do I
> > miss?
>
> this should be enough. But you need to fill in the correct params for
> bdaddr and channel. What did "hcidump -x" say?

address@hidden:~/gnokii-bluetooth$ ./gnokii/gnokii --identify
GNOKII Version 0.5.0pre7
[...]
Adding key/value rfcomm_cn/1
Adding key/value bt_address/00:02:EE:12:9B:F9
[...]
Initializing AT capable mobile phone ...
Serial device: opening device /dev/rfcomm0
Can't connect: Host is down
[...]
address@hidden:~$ hcidump -x
HCIDump - HCI packet analyzer ver 1.5
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Command Status(0x0f) plen 4
  00 01 05 04
> HCI Event: Connect Complete(0x03) plen 11
  04 00 00 00 02 EE 12 9B F9 01 00
address@hidden:~$ /sbin/lsmod
Module                  Size  Used by
l2cap                  16768   2 (autoclean)
rfcomm                 29552   0 (autoclean)
hci_usb                 7424   1
bluez                  30384   3 [l2cap rfcomm hci_usb]
uhci                   25024   0 (unused)
address@hidden:~$ ps xa
  PID TTY      STAT   TIME COMMAND
[...]
 1882 ?        SW     0:00 [krfcommd]
 1887 ?        S      0:00 hcid: processing events
 1891 ?        S      0:00 sdpd
[...]

bluetooth_open() is called with:
bluetooth_open(&state->config.bt_address, state->config.rfcomm_cn, state);

Adding:
        dprintf("%s\n", batostr(&raddr.rc_bdaddr));
        dprintf("%d\n", raddr.rc_channel);
before connect() in bluetooth_open() shows:
00:02:EE:12:9B:F9
1

pkot
PS. Do you ever sleep? It doesn't matter when I send you an email and I
get the response quite soon :-)
-- 
mailto:address@hidden :: mailto:address@hidden
http://kt.linuxnews.pl/ :: Kernel Traffic po polsku