From: Martin Stolle <mstoll@sus.mcgill.ca>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] help with Logitech Travel Mouse
Date: Thu, 27 Sep 2007 09:42:57 -0400 [thread overview]
Message-ID: <20070927134257.GA32196@sus.mcgill.ca> (raw)
In-Reply-To: <1190878752.6484.48.camel@aeonflux.holtmann.net>
On Thu, Sep 27, 2007 at 09:39:12AM +0200, Marcel Holtmann wrote:
> >
> > Thank you very much. I didn't realize that hidd were supposed to still
> > work. I will look into writing a python tool that does what I want to
> > do. However, I still don't quite understand why the hidd behavior has
> > changed and/or why it is incorrect to use them more then once. In
> > particular, in the case where a device (keyboard/mouse) was once paired
> > with a computer, but then has been re-paired with another computer. If
> > I want to reconnect the keyboard/mouse to the first computer, wouldn't I
> > have to re-issue a hidd --connect <MAC> ? (or the equivalent D-Bus
> > calls?)
>
> the HID devices are not designed to work like this. Period. They only
> support one binding with a host system. You try to make it work with a
> scenario it is not designed for. If you need details, check the
> Bluetooth HID specification.
>
I understand that HID devices only support one binding at a time. But
if I want to use the same keyboard with two systems, not at the same
time but back and forth, then I should be able to re-authenticate it
with the previous system. This is a use case that totally makes sense
and works fine. It used to work fine between two Linux system, two
Windows system and a Windows and Linux system. I just had one keyboard
and whenever I wanted to use it with another system, I'd reset the
keyboard and re-pair it with the system at hand. This is definitely
possible and I am sure that the specifications allow for pairing with a
system that was previously paired with in case the HID device lost its
pairing.
(And no, I don't expect it two work with two systems at the same time or
interchangeably without re-pairing. I completely understand that the
HID device can only be paired with one system at any one moment in time)
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-09-27 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:13 [Bluez-users] help with Logitech Travel Mouse Jared Greenwald
2007-09-24 19:22 ` Martin Stolle
2007-09-24 19:33 ` Jared Greenwald
2007-09-24 22:14 ` Marcel Holtmann
2007-09-24 22:21 ` Martin Stolle
2007-09-24 23:12 ` Marcel Holtmann
2007-09-24 23:21 ` Martin Stolle
2007-09-25 11:50 ` Jared Greenwald
2007-09-25 12:24 ` Claudio Takahasi
2007-09-25 12:34 ` Martin Stolle
2007-09-26 11:30 ` Stefan Seyfried
2007-09-26 14:05 ` Martin Stolle
2007-09-26 22:06 ` Marcel Holtmann
2007-09-26 22:18 ` Martin Stolle
2007-09-27 7:39 ` Marcel Holtmann
2007-09-27 13:42 ` Martin Stolle [this message]
2007-09-27 23:08 ` Marcel Holtmann
2007-09-25 12:41 ` Jared Greenwald
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=20070927134257.GA32196@sus.mcgill.ca \
--to=mstoll@sus.mcgill.ca \
--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