On Fri, 19 Jul 2013, Peter Hurley wrote:
As far as getting printk output from a custom kernel, I think that may
be beyond the reporter's capability. Perhaps one of the Ubuntu devs
triaging this bug could provide a test kernel for the OP with those
options on.
Joseph, would you
On 07/22/2013 07:44 AM, Jiri Kosina wrote:
On Fri, 19 Jul 2013, Peter Hurley wrote:
As far as getting printk output from a custom kernel, I think that may
be beyond the reporter's capability. Perhaps one of the Ubuntu devs
triaging this bug could provide a test kernel for the OP with those
On Thu, 18 Jul 2013, Nestor Lopez Casado wrote:
This reverts commit 8af6c08830b1ae114d1a8b548b1f8b056e068887.
This patch re-adds the workaround introduced by 596264082f10dd4
which was reverted by 8af6c08830b1ae114.
The original patch 596264 was needed to overcome a situation where
the
Hi,
On 07/19/2013 04:26 PM, Felipe Balbi wrote:
Hi,
[...]
please don't remove this code. It'll be good to have this around when we
move the driver to threaded IRQs without IRQF_ONESHOT. In fact, it would
be very simple to implement such a change, wanna take it up ?
It should be doable in few
On Mon, Jul 22, 2013 at 7:35 AM, Jiri Kosina jkos...@suse.cz wrote:
Linus -- could you please by any chance test whether the two patches in
that branch make the problem you are observing any better? (and no, this
is not a pull request yet).
It's still not clear whether we are chasing two
Hi,
On Mon, Jul 22, 2013 at 08:25:05PM +0300, Illia Smyrnov wrote:
please don't remove this code. It'll be good to have this around when we
move the driver to threaded IRQs without IRQF_ONESHOT. In fact, it would
be very simple to implement such a change, wanna take it up ?
It should be
[Note: bcc'd linux-input, wayland-devel and xorg-devel since those are the
expected interested parties. Apologies if you get this email multiple times,
I won't do this in the future. Future announcements will only go to
input-to...@lists.freedesktop.org]
This is the first release for libevdev, a
On Mon, Jul 15, 2013 at 03:37:09PM +0200, Benjamin Tissoires wrote:
Evemu [1] uses uinput to replay devices traces it has recorded. However,
the way evemu uses uinput is slightly different from how uinput is
supposed to be used.
Evemu creates the device node through uinput, bu inject events
