From: Antonio Ospite <ospite@studenti.unina.it>
To: Christian Birchinger <joker@netswarm.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Auto trust entry remove
Date: Mon, 24 May 2010 13:10:10 +0200 [thread overview]
Message-ID: <20100524131010.631647d3.ospite@studenti.unina.it> (raw)
In-Reply-To: <20100524105659.GA19294@netswarm.net>
[-- Attachment #1: Type: text/plain, Size: 2617 bytes --]
On Mon, 24 May 2010 12:56:59 +0200
Christian Birchinger <joker@netswarm.net> wrote:
> On Mon, May 24, 2010 at 11:31:22AM +0200, Antonio Ospite wrote:
>
> First of all i know what prevented the BT HID from being added.
> The netlink plugin was disabled and that's required for this
> to work. Really stupid mistake.
>
> The device gets added now and for the first time i get input data
> from it.
>
Good.
> > On Mon, 24 May 2010 10:53:44 +0200
> > Christian Birchinger <joker@netswarm.net> wrote:
> >
> > Christian, I can only say that it works for me with the kernel patches
> > from http://lists.ozlabs.org/pipermail/cbe-oss-dev/2010-May/007274.html
> > and an updated sixaxis-cable patch which I haven't published yet
> > because it was not final and I didn't want to leave temporary stuff,
> > which could be soon deprecated, archived on the Internet; that may
> > confuse people.
>
> Thanks for the hint, i just patched my kernel an rebooted. This is the
> output when i plug the controller over USB:
>
> sony 0003:054C:0268.0007: input,hiddev96,hidraw3: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:1a.0-1.3.4/input0
> sony 0003:054C:0268.0007: Calling sixaxis_set_operational_usb
> sony 0003:054C:0268.0007: Sony PS3 Controller bdaddr: <controller addr>
>
> So it works fine.
>
Yes.
> > Let me know if you want me to send this updated sixaxis-cable to you
> > privately.
>
> Yes, that would be interesting. Is there some default location to find
> the recent public release of it too? I'm alsways exctracting it from
> the Fedora srpm.
>
The one from Fedora srpm uses libusb and hence has to detach and
reattach the usbhid driver in order to work. With my patch+my
sixaxis-cable plugin libusb is not needed anymore, but I am not
publishing it because I didn't receive feedback on those kernel patches
from kernel people, and I feel that means extending hidraw should be the
way, I just haven't found the time to work on it yet. I am sending the
sixaxis-cable plugin to you in another mail just to show the concept,
don't distribute it yet, keep in mind that it should be changed to use
hidraw once I finished with this.
> Thanks a lot for your help
> Bye, Christian
>
You're welcome.
Regards,
Antonio
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-05-24 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 8:33 Auto trust entry remove Christian Birchinger
2010-05-24 8:53 ` Christian Birchinger
2010-05-24 9:31 ` Antonio Ospite
2010-05-24 10:56 ` Christian Birchinger
2010-05-24 11:10 ` Antonio Ospite [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=20100524131010.631647d3.ospite@studenti.unina.it \
--to=ospite@studenti.unina.it \
--cc=joker@netswarm.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;
as well as URLs for NNTP newsgroup(s).