linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Hugo Osvaldo Barrera <hugo@osvaldobarrera.com.ar>
Cc: Nestor Lopez Casado <nlopezcasad@logitech.com>,
	linux-input@vger.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@enac.fr>,
	671292@bugs.debian.org
Subject: Re: [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm
Date: Sun, 6 May 2012 01:23:10 -0500	[thread overview]
Message-ID: <20120506062309.GB26002@burratino> (raw)
In-Reply-To: <4FA6162F.1020408@osvaldobarrera.com.ar>

Hugo Osvaldo Barrera wrote:
> On 2012-05-06 02:55, Jonathan Nieder wrote:

>> The pairing (...add_djhid_device) happens during initialization,
>> before the mouse is turned on...
>
> I don't think I quite follow there.  By "pairing" I though you meant
> when the receiver connects to the mouse.  How can the pairing be done
> while the device is off?  Or what am I missing here?

I'm guessing the actual pairing happens without Linux being involved.
Then the driver sends a "get paired devices" request during
initialization and the device sends the "device paired" notifications
I'm interested in in response.

> Do I need to apply only this patch, or both the previous one and this one?

Only this patch.

Cheers,
Jonathan

  reply	other threads:[~2012-05-06  6:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120503052000.GC15205@burratino>
     [not found] ` <20120503052420.GD15205@burratino>
     [not found]   ` <4FA217B7.7070908@osvaldobarrera.com.ar>
2012-05-03  5:50     ` [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm Jonathan Nieder
     [not found]       ` <CAE7qMrqtmu+bYYYp43s7Ek=UxfUG8HzwQSQBsdCGcVCBzCMQQw@mail.gmail.com>
2012-05-03 13:08         ` Jonathan Nieder
2012-05-03 13:13           ` Jonathan Nieder
2012-05-04  2:40             ` Bug#671292: " Hugo Osvaldo Barrera
2012-05-04  7:41               ` Jonathan Nieder
2012-05-04  8:10                 ` Hugo Osvaldo Barrera
2012-05-04  8:14                   ` Hugo Osvaldo Barrera
2012-05-04  8:36                     ` Jonathan Nieder
2012-05-04 10:16                       ` Nestor Lopez Casado
2012-05-04 10:49                         ` Jonathan Nieder
2012-05-06  3:14         ` Hugo Osvaldo Barrera
2012-05-06  5:55           ` Jonathan Nieder
2012-05-06  6:11             ` Hugo Osvaldo Barrera
2012-05-06  6:23               ` Jonathan Nieder [this message]
2012-05-11  5:06                 ` Hugo Osvaldo Barrera
2012-05-11  6:38                   ` Nestor Lopez Casado
2012-05-11  7:22                     ` [PATCH/RFC] HID: logitech: read all 32 bits of report type bitfield Jonathan Nieder
2012-05-11  7:36                       ` Nestor Lopez Casado
2012-05-11  7:43                         ` Jonathan Nieder
2012-05-11  7:39                       ` [PATCH/RFC v2] " Jonathan Nieder
2012-05-11 10:55                         ` Jiri Kosina
2012-05-11 12:50                         ` Hugo Osvaldo Barrera

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=20120506062309.GB26002@burratino \
    --to=jrnieder@gmail.com \
    --cc=671292@bugs.debian.org \
    --cc=benjamin.tissoires@enac.fr \
    --cc=hugo@osvaldobarrera.com.ar \
    --cc=linux-input@vger.kernel.org \
    --cc=nlopezcasad@logitech.com \
    /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;
as well as URLs for NNTP newsgroup(s).