From: Simon Kenyon <simon@koala.ie>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Sony BD Remote (the saga continues)
Date: Fri, 28 Nov 2008 22:43:16 +0000 [thread overview]
Message-ID: <49307404.6080003@koala.ie> (raw)
In-Reply-To: <1227882126.26649.1099.camel@cookie.hadess.net>
Bastien Nocera wrote:
> On Fri, 2008-11-28 at 10:54 +0000, Simon Kenyon wrote:
>
>> Simon Kenyon wrote:
>>
>>> so i decided to start working my way through the code and found
>>> references to uinput in input/device.c
>>> this gave me another keyword to use in google and lo and behold this
>>> popped up:
>>>
>>> Fri Oct 17 2008 - Bastien Nocera <bnocera@redhat.com
>>> <mailto:bnocera@redhat.com>> - 4.14-2
>>> - Add script to autoload uinput on startup, so the PS3 remote
>>> works out-of-the-box
>>>
>>>
>>> sure enough i did not have this module in my kernel.
>>> just building now in hope that this might be the issue
>>>
>> well that got me nowhere - still no events
>> but at least i now have a /dev/input/uinput
>>
>
> You need to press buttons on the remote for it to connect to the
> computer. It will disconnect automatically after some time of idleness.
>
> After that you need to use a new enough X server, or LIRC to get the
> events to your X applications.
>
what causes the /dev/input/eventX file to be created?
ie. is it bluetoothd or hidd?
next prev parent reply other threads:[~2008-11-28 22:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 10:14 Sony BD Remote (the saga continues) Simon Kenyon
2008-11-28 10:54 ` Simon Kenyon
2008-11-28 12:09 ` Simon Kenyon
2008-11-28 13:16 ` Simon Kenyon
2008-11-28 13:21 ` Jelle de Jong
2008-11-28 13:53 ` Simon Kenyon
2008-11-28 14:07 ` Jelle de Jong
2008-11-29 16:55 ` Jelle de Jong
2008-11-30 10:52 ` Simon Kenyon
2008-11-30 13:31 ` Jelle de Jong
2008-11-30 17:02 ` Simon Kenyon
2008-11-28 14:22 ` Bastien Nocera
2008-11-28 22:43 ` Simon Kenyon [this message]
2008-11-29 0:59 ` Bastien Nocera
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=49307404.6080003@koala.ie \
--to=simon@koala.ie \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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