From: Marcel Holtmann <marcel@holtmann.org>
To: Thomas Liebetraut <thomas@tommie-lie.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: How to set link policy with Logitech diNovo dongle
Date: Fri, 12 Dec 2008 19:43:53 +0100 [thread overview]
Message-ID: <1229107433.22285.138.camel@violet.holtmann.net> (raw)
In-Reply-To: <4942AFFC.30307@tommie-lie.de>
Hi Thomas,
> > Problem is that this particular firmware is a custom build for Logitech
> > (or beta firmware) as it looks like. Also you have other problems with
> > not having AFH enabled when you have WiFi around.
> >
> > I think that I do have the exact same mouse and keyboard at home
> > somewhere. But not supporting Default Link Policy is just pure stupid.
> So I better go any buy a new dongle? Or do you see any chance to make
> this old one work?
> Any recommendations for a new dongle? Are those small cheap noname
> dongles for 8 Euros (10 USD) any good? Or does quality have its price?
as long as you get one with a CSR or Broadcom chip and Bluetooth 2.1
your are in a good position. The new ones are really really tiny and
stick only out 1cm or so. Personally I prefer CSR based dongles.
Regards
Marcel
next prev parent reply other threads:[~2008-12-12 18:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 19:10 How to set link policy with Logitech diNovo dongle Thomas Liebetraut
2008-12-08 19:51 ` Marcel Holtmann
2008-12-08 22:24 ` Thomas Liebetraut
2008-12-09 19:52 ` Thomas Liebetraut
2008-12-12 1:48 ` Marcel Holtmann
2008-12-12 17:26 ` Thomas Liebetraut
2008-12-12 17:48 ` Marcel Holtmann
2008-12-12 18:02 ` Thomas Liebetraut
2008-12-12 18:07 ` Marcel Holtmann
2008-12-12 18:39 ` Thomas Liebetraut
2008-12-12 18:43 ` Marcel Holtmann [this message]
2008-12-13 16:41 ` Thomas Liebetraut
2008-12-12 18:30 ` Jelle de Jong
2008-12-12 19:34 ` Thomas Liebetraut
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=1229107433.22285.138.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=thomas@tommie-lie.de \
/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