public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] help with Logitech Travel Mouse
Date: Thu, 27 Sep 2007 09:39:12 +0200	[thread overview]
Message-ID: <1190878752.6484.48.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20070926221821.GA24681@sus.mcgill.ca>

Hi Martin,

> > For the hidd case we provide smooth transition. So once you connected
> > via --search and --connect the new input service will pick up that HID
> > device on next boot and make it work. However --search and --connect and
> > are one-time commands only. No matter what you think or what you want or
> > what you read somewhere else. If you use them in a wrong why, then that
> > is your problem.
> > 
> 
> 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.

Regards

Marcel



-------------------------------------------------------------------------
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

  reply	other threads:[~2007-09-27  7:39 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 [this message]
2007-09-27 13:42                             ` Martin Stolle
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=1190878752.6484.48.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --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