From: Jelle de Jong <jelledejong@powercraft.nl>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Sony BD Remote Control still does not make input event, what part of the driver is driver missing?
Date: Tue, 10 Feb 2009 15:06:46 +0100 [thread overview]
Message-ID: <499189F6.7010305@powercraft.nl> (raw)
In-Reply-To: <1232982561.3330.3777.camel@cookie.hadess.net>
Bastien Nocera wrote:
> On Tue, 2009-01-20 at 00:27 +0100, Jelle de Jong wrote:
>> Hi all,
>>
>> I thought I gave my Sony PS3 Bluetooth remote an other try, see all my
>> previous messages trials and bug reports back in the mail archive.
>>
>> The device still does not create an input event that can be used out of
>> the box. What parts are missing to get this working?
>
> modprobe uinput?
>
>> The device connects with the gnome bluetooth tool, you see the connect
>> icon go on very short then the connect icons goes away. hcitool con also
>> does not show the device and there is no input event created.
>>
>> What is going on here? And what need to be done here.
>
Hi Bastien,
I did some more testing and loaded the uinput module, put the device
in pairing/connecting mode, then started bluetooth-applet. Connected
the device and stil NO input device is created and uninput is not used.
$ lsmod | grep uinput
uinput 6592 0
Could somebody show me any prove that it is possible to create an
input device with the Sony BD Remote Control? A list of the below
command for the device would be nice to.
evtest /dev/input/eventX
Thanks in advance,
Jelle
prev parent reply other threads:[~2009-02-10 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 23:27 Sony BD Remote Control still does not make input event, what part of the driver is driver missing? Jelle de Jong
2009-01-26 14:05 ` Jelle de Jong
2009-01-26 15:09 ` Bastien Nocera
2009-02-10 14:06 ` Jelle de Jong [this message]
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=499189F6.7010305@powercraft.nl \
--to=jelledejong@powercraft.nl \
--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