From: Alexander Holler <holler@ahsoftware.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Tim Tisdall <tim.tisdall@flemingcollege.ca>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: l2cap sockets not properly multiplexed on ARM
Date: Thu, 31 Oct 2013 00:06:02 +0100 [thread overview]
Message-ID: <527190DA.6000805@ahsoftware.de> (raw)
In-Reply-To: <4A213FF7-48BA-4906-8868-7C3A227EF954@holtmann.org>
Am 30.10.2013 20:40, schrieb Marcel Holtmann:
...
>> So it's perfectly clear: This all works fine on an x86 machine, but is an issue on ARM
...
> Do you have the chance to run bluetooth-next tree for testing purposes?
As Anderson Lizardo already mentioned, maybe first verify that the x86
kernel 3.4 doesn't have the same problem and that it's really a problem
of the ARM kernel. Up to now he didn't say what kernel version he uses
on x86.
Regards.
Alexander Holler
next prev parent reply other threads:[~2013-10-30 23:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 20:44 l2cap sockets not properly multiplexed on ARM Tim Tisdall
2013-10-30 11:24 ` Alexander Holler
2013-10-30 11:46 ` Alexander Holler
2013-10-30 13:15 ` Tim Tisdall
2013-10-30 14:16 ` Alexander Holler
2013-10-30 15:06 ` Tim Tisdall
2013-10-30 15:10 ` Tim Tisdall
2013-10-30 15:16 ` Tim Tisdall
2013-10-30 18:36 ` Anderson Lizardo
2013-10-30 19:40 ` Marcel Holtmann
2013-10-30 20:45 ` Tim Tisdall
2013-10-30 20:57 ` Marcel Holtmann
2013-10-30 23:06 ` Alexander Holler [this message]
2013-10-31 13:31 ` Tim Tisdall
2013-10-31 14:14 ` Tim Tisdall
2013-10-31 14:18 ` Tim Tisdall
2013-10-31 14:19 ` Marcel Holtmann
2013-10-31 14:20 ` Marcel Holtmann
2013-10-31 14:29 ` Tim Tisdall
2013-10-31 14:41 ` Marcel Holtmann
2013-11-01 11:03 ` Anderson Lizardo
2013-11-01 13:35 ` Tim Tisdall
2013-11-01 14:11 ` Tim Tisdall
-- strict thread matches above, loose matches on Subject: below --
2013-10-29 13:43 Tim Tisdall
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=527190DA.6000805@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=tim.tisdall@flemingcollege.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.