Re: [Bluez-users] SDP problems on embedded device

Marcel Holtmann
2004-07-21T10:04:51Z

Hi Rolf,

> >>>Try using 2.4.19-mh14 and show us the output of "hciconfig -a" on your
> >>>Cerfcube. Is the Cerfcube a big endian machine?
> >>
> >>After compiling a new kernel and reflashing:
> >
> > does this kernel work?
>
> Yes (but I haven't tested much), although I get this error message when
> booting:

I meant, if the SDP browsing works with that kernel patch?

> Calculating module dependencies... depmod: *** Unresolved symbols in
> /lib/modules/2.4.19-rmk6-pxa1-cerf1/kernel/drivers/bluetooth/bfusb.o

This can happen. You won't need the bfusb.o driver. Try a clean compile.

> A couple of months ago when I first tried to get sdp to work, I also
> randomly tried the mh13- and mh15-patches but with the same outcome as
> with the mh14- and mh17-patches.

So is the mh14 working for you or not? I don't get the correct point
here.

> > Please try another dongle with at least HCI 16.4 firmware.
>
> Sorry for being a little bit puzzled now. How do I see what the firmware
> version is for my current dongle? I translate the HCI Rev hex number to
> 469 in decimal so should I just put the decimal point after the 4?
>
> At the moment I also have another USB dongle available and the output
> from "hciconfig hci0 version" is
>
> [root@xscale3 /root]# hciconfig hci0 version
> hci0: Type: USB
> BD Address: 00:0C:76:B1:05:74 ACL MTU: 192:8 SCO MTU: 64:8
> HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP
> Subver: 0x20d
> Manufacturer: Cambridge Silicon Radio (10)
>
> Which give HCI Rev number 525 in decimal. Are my dongles really that
> antique?

You can use "hciconfig hci0 revision" or look it up on my CSR page.

> Final question. I'm curious about why I should try the mh14-patch? Do
> one experience subtle differences between the output from hciconfig?

I think that this change "Fix non-blocking socket race conditions" could
have caused some problems. One part of it already has :(

Regards

Marcel