public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Simon Kenyon <simon@koala.ie>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Sony BD Remote (the saga continues)
Date: Sat, 29 Nov 2008 00:59:41 +0000	[thread overview]
Message-ID: <1227920381.26649.1749.camel@cookie.hadess.net> (raw)
In-Reply-To: <49307404.6080003@koala.ie>

On Fri, 2008-11-28 at 22:43 +0000, Simon Kenyon wrote:
> Bastien Nocera wrote:
<snip>
> > 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?

It is obviously bluetoothd (actually bluetoothd's input plugin) as I've
said a couple of days ago (and on numerous occasions on this list) that
hidd has no code to handle the PS3 BD remote's protocol. If you're using
hidd, it won't ever work, period.

If the PS3 remote isn't connected properly, it won't show up in
bluetooth-properties.


      reply	other threads:[~2008-11-29  0:59 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
2008-11-29  0:59       ` Bastien Nocera [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=1227920381.26649.1749.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=simon@koala.ie \
    /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