From: Marcel Holtmann <marcel@holtmann.org>
To: "Rolf E. Thorup" <rolft@daimi.au.dk>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] SDP problems on embedded device
Date: Wed, 21 Jul 2004 12:04:51 +0200 [thread overview]
Message-ID: <1090404291.21683.81.camel@pegasus> (raw)
In-Reply-To: <40FE3ACF.4030608@daimi.au.dk>
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
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-07-21 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 19:38 [Bluez-users] SDP problems on embedded device Rolf E. Thorup
2004-07-19 20:53 ` Marcel Holtmann
2004-07-20 10:31 ` Rolf E. Thorup
2004-07-20 14:47 ` Marcel Holtmann
2004-07-20 17:10 ` Rolf E. Thorup
2004-07-20 17:43 ` Marcel Holtmann
2004-07-21 9:43 ` Rolf E. Thorup
2004-07-21 10:04 ` Marcel Holtmann [this message]
2004-07-21 10:56 ` Rolf E. Thorup
2004-07-21 12:18 ` Marcel Holtmann
2004-07-21 12:30 ` Rolf E. Thorup
2004-07-28 14:05 ` Rolf E. Thorup
2004-07-28 18:57 ` 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=1090404291.21683.81.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=rolft@daimi.au.dk \
/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