From: Walt Shekrota <innkeep@capital.net>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Ubuntu 6.06 and bluez setup problem?
Date: Mon, 05 Feb 2007 18:03:10 -0500 [thread overview]
Message-ID: <200702051803.10789.innkeep@capital.net> (raw)
how do I determine the proper class as used in hcid.conf
and channel as used in rfcomm.conf?
I think I have found my problem but can't confirm it yet.
I have 2 dongles
one a Cellink BTA-3120 (not a 3000) so probably the manaufacturer has changed
the chipset
another a trendnet 102ub
I thought this should work being it is listed in the Holtmann feature list?
Perhaps in later revisions they too changed chipset?
Or are only some of these dongles listed in the feature list usable for Linux?
If so how do you tell?
At any rate I've chickened out before I have a box of useless dongles I'll go
for the DBT-120 at proper revision to be sure.
If someone could kindly post some info or a confirmation I might be right it
would be helpful. I've got to say this is one of the most difficult areas in
the linux user arena. Somehow it has to be made more simple.
Possibly supporting more chipsets would help. Is this a future work item?
Thanks.
-Walt
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-02-05 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 23:03 Walt Shekrota [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-02 15:49 [Bluez-users] Ubuntu 6.06 and bluez setup problem? Walt Shekrota
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=200702051803.10789.innkeep@capital.net \
--to=innkeep@capital.net \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox