public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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:07:46 +0100	[thread overview]
Message-ID: <1229105266.22285.116.camel@violet.holtmann.net> (raw)
In-Reply-To: <4942A74E.2020409@tommie-lie.de>

Hi Thomas,

> > this is a really old dongle.
> Don't know exactly, about 4 years I guess. It's from the first DiNovo
> Media Desktop (neither Laser nor 2.0).
> 
> > Check hciconfig hci0 revision (as root) if
> > it is either a BlueCore01 or BlueCore02.
> | thomas@Majestix:~$ sudo hciconfig hci0 revision
> | hci0:   Type: USB
> |         BD Address: 00:07:61:19:49:79 ACL MTU: 192:8 SCO MTU: 64:8
> |         Build 846
> |         Chip version: BlueCore02-External
> |         Max key size: 56 bit
> |         SCO mapping:  HCI
> 
> > No idea why the Default Link Policy commands is not implemented here.
> > That is really strange.
> Isn't there some other way to get smooth communication with my MX900?
> After all, the Bluetooth Travel Mouse works fine with the exact same
> dongle after just reconnecting it.

not really. It is tricky and I am not willing to go back to the per
connection link policy setup, because that interferes with how with
setup Bluetooth 2.1 devices.

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.

Regards

Marcel



  reply	other threads:[~2008-12-12 18:07 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 [this message]
2008-12-12 18:39               ` Thomas Liebetraut
2008-12-12 18:43                 ` Marcel Holtmann
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=1229105266.22285.116.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