From: Szymon Janc <szymon.janc@tieto.com>
To: Andrea <mariofutire@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: partial success with PS3 sixaxis
Date: Fri, 28 Feb 2014 11:35:29 +0100 [thread overview]
Message-ID: <1521205.0Q940hgGyU@uw000953> (raw)
In-Reply-To: <53086B93.3080503@gmail.com>
Hi Andrea,
On Saturday 22 of February 2014 09:19:15 Andrea wrote:
> On 20/02/14 09:47, Szymon Janc wrote:
> > Hi Andrea,
> >
> >
> > This is a known regression on kernels >3.9. Should be fixed in 3.15 AFAIR.
> >
>
> you really mean 3.15? not even 3.14?
AFAIK yes, this regression was only spotted in mid December when sixaxis
patches were submitted and proper fix turns out to be not that trivial.
> then, my last issue is the following:
>
> on Fedora 19 x86 things work with a Bluetooth 4.0 dongle
>
> 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
>
> running 3.12.11 (Fedora version)
>
>
>
> unfortunately on a Raspberry Pi ARM6, Arch Linux with kernel 3.13.3 I get a strange kernel oops
> after a random time of successful usage (could be 1 minute or 2 days)
>
> I struggle to get a meaningful stack trace (the whole system dies, need to attach a serial console),
> would you know of any issues on this architecture? it seems to be a NULL pointer exception.
> The same crash happens with a different dongle (older bluetooth 2 from broadcom)
I haven't seen any issues on my PC but I wasn't using it on any ARM device.
--
Best regards,
Szymon Janc
prev parent reply other threads:[~2014-02-28 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 21:31 partial success with PS3 sixaxis Andrea
2014-02-13 9:25 ` Szymon Janc
2014-02-15 12:10 ` Andrea
2014-02-28 10:47 ` Szymon Janc
2014-02-28 21:20 ` Andrea
2014-02-15 20:41 ` Andrea
2014-02-15 20:49 ` Andrea
2014-02-20 9:47 ` Szymon Janc
2014-02-22 9:19 ` Andrea
2014-02-28 10:35 ` Szymon Janc [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=1521205.0Q940hgGyU@uw000953 \
--to=szymon.janc@tieto.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mariofutire@gmail.com \
/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).