From: "Fintan McEvoy" <fintan.mcevoy@ul.ie>
To: <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] Bluetooth 1.2 device
Date: Thu, 28 Apr 2005 13:39:19 +0100 [thread overview]
Message-ID: <002501c54bef$4c4feae0$d24bc988@computernetworks> (raw)
In-Reply-To: <4270D347.1030204@gmx.ch>
Thanks a million Marco,
You have answered all my questions,
Help is much appreciated.
Regards,
Fintan
-----Original Message-----
From: bluez-users-admin@lists.sourceforge.net
[mailto:bluez-users-admin@lists.sourceforge.net] On Behalf Of Marco
Trudel
Sent: 28 April 2005 13:13
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluetooth 1.2 device
Hello Fintan
Fintan McEvoy wrote:
> Hi,
> I'm sure this is a common question but I'm looking for a bluetooth
> version 1.2 device that works well with bluez and under a kernel not
> over 2.4.29 . Can anyone make a good suggestion. Options I have looked
> at so far include DBT-120 and upgrading firmware.
The D-Link DBT-120 will probably be the best choice.
After an firmware update you have to reset it to hci bootmode (or use
hid2hci). Marcel wrote the pskey tool for this, it's in the cvs.
> Questions I have about
> that include, do I need a MAC to do this
No. There are a lot of utilities for windows to do that. Widcomm (I
think >
3.0) has an updater included. I always use that.
There's also the btdfu tool for linux, but as much as I know it's not
that
recommended. I would suggest the widcomm one.
> and will it work with 2.4.29 .
yes.
> In fact will it work with Bluez at all this way. The other device I
have
> looked at is the newly SIG approved F8T009 belkin device. This seems
to
> use Broadcom BCM2035 chipset.
Broadcom's don't work that great with bluez. If you can, you really
should
avoid them.
> I think Bluez works when this chipset uses
> Bluetooth v1.1 . Is this correct? Will it work if it is using v 1.2 .
there are problem with both.
> I really do need to get a bluetooth 1.2 device that works
as
> I'm setting up a testbed for research here in University of Limerick,
> Ireland. Any suggestions on what device to buy will be greatly
> appreciated.
regards
Marco
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-04-28 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 11:34 [Bluez-users] Bluetooth 1.2 device Fintan McEvoy
2005-04-28 12:12 ` Marco Trudel
2005-04-28 12:39 ` Fintan McEvoy [this message]
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='002501c54bef$4c4feae0$d24bc988@computernetworks' \
--to=fintan.mcevoy@ul.ie \
--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