From: "Rickard Borgmäster" <doktorn@sub.nu>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Broadcom 2035 USB Dongle
Date: Tue, 21 Mar 2006 17:23:03 +0100 [thread overview]
Message-ID: <dvp997$em0$1@sea.gmane.org> (raw)
Hello,
I've just spent a few hours struggling to get GPRS Bluetooth connections
to work with a Broadcom 2035 (OEM) USB Dongle and my Nokia 6230i. The
dongle address is for some reason set to 00:00:00:00:00:00. "hcitool
can" and similar commands return "Device not available: No such device".
While I was about to think that this dongle wouldn't work with
linux/BlueZ at all, I accidently addressed it explicitly with "hcitool
-i hci0 scan" and voila... it works.
Though the null-set address and such, I can connect to my provider and
everything. So this device works well, you developers probably just need
to "recognize" it better and find out how to make sure it get's a proper
address.
Please tell me if I can help you out. I have no programming skills but I
can always try out some code or so :-)
Best regards
Rickard Borgmäster
Sweden
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2006-03-21 16:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='dvp997$em0$1@sea.gmane.org' \
--to=doktorn@sub.nu \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.