From: Jonathan Nieder <jrnieder@gmail.com>
To: Nestor Lopez Casado <nlopezcasad@logitech.com>
Cc: Hugo Osvaldo Barrera <hugo@osvaldobarrera.com.ar>,
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: Fri, 4 May 2012 05:49:02 -0500 [thread overview]
Message-ID: <20120504104902.GA7766@burratino> (raw)
In-Reply-To: <CAE7qMrpWMJ=U3H3BBkxXGskNnNG7ZURS44Euh0_LZhq6ucBmpA@mail.gmail.com>
Nestor Lopez Casado wrote:
> Would you be able to test the following patch on both systems and let
> us know about the result?
Instructions for Hugo:
# prerequisites
apt-get install git build-essential
# get the kernel history, if you don't already have it
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
# latest mainline kernel
cd linux
git fetch origin
git checkout origin/master
# configure
cp /boot/config-$(uname -r) .config; # current configuration
scripts/config --disable DEBUG_INFO; # smaller build
make localmodconfig; # minimize configuration
# apply patch
git apply --index /path/to/patch
# build
make deb-pkg; # optionally with -j<num> for parallel build
# test
dpkg -i ../<name of package>; # as root
reboot
# to unapply patch:
cd linux
git reset --hard origin/master
# when you want to build again:
make deb-pkg; # maybe with -j4
dpkg -i ../<name of package>; # as root
reboot
I would also be interested in a capture of the pairing event, if possible:
(remove mouse battery or bring mouse out of range)
mount -t debugfs debugfs /sys/kernel/debug
ls /sys/kernel/debug/hid/
modprobe -r hid_logitech_dj
modprobe hid_logitech_dj
cat /sys/kernel/debug/hid/<device name>/events >events.captured
(insert mouse battery or bring mouse within range)
^C
Jonathan
next prev parent reply other threads:[~2012-05-04 10:49 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 [this message]
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
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=20120504104902.GA7766@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).