From: Simon Kenyon <simon@koala.ie>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Sony BD Remote (the saga continues)
Date: Fri, 28 Nov 2008 13:16:40 +0000 [thread overview]
Message-ID: <492FEF38.3020702@koala.ie> (raw)
In-Reply-To: <492FDF90.9010305@koala.ie>
Simon Kenyon wrote:
> 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
>>
>> will have to dig further and see what bluetoothd does with it
>
> do i have to have something in one of the /etc/bluetooth/*.conf files
> specific to the BD Remote?
>
> could somebody who has this working please post the contents of
> /etc/bluetooth/*.conf?
> or do i need something to be configured in dbus?
>
> i cannot see how any of the code in input/fakehid.c gets called. i've
> put a lot of debug statements in there; trying to understand the logic.
> i don't see any devices getting registered
i left bluetooth-wizard running for 10 minutes while i did something else
maybe i pressed <start> and <enter> during that period. i cannot remember.
anyway, the BD Remote appeared in the bluetooth-wizard setup window.
when i typed forward it said it was successful. what did it do?
now i try again and the remote is in the window from the start, but when
i select it and go forward, it now says "Pairing with BD Remote Control
failed".
what does that mean?
still don't know what has happened to /dev/input/event<x> where <x> is
usually 7 in my case. i only ever see it if i type hidd --search and
<start> and <enter>
if i should not use it, why is it built and installed?
regards
--
simon
next prev parent reply other threads:[~2008-11-28 13:16 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 [this message]
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
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=492FEF38.3020702@koala.ie \
--to=simon@koala.ie \
--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