Return-Path: <cyrus@holtmann.org>
Message-ID: <527114A4.5010207@ahsoftware.de>
Date: Wed, 30 Oct 2013 15:16:04 +0100
From: Alexander Holler <holler@ahsoftware.de>
MIME-Version: 1.0
To: Tim Tisdall <tim.tisdall@flemingcollege.ca>
CC: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: l2cap sockets not properly multiplexed on ARM
References: <D9B9EB3A112B8F489DFFA00A6D5C0FE20324078F@AD-BR-EX-2.adroot.flemingc.local> <5270EC62.6070705@ahsoftware.de>,<5270F19A.4030408@ahsoftware.de> <D9B9EB3A112B8F489DFFA00A6D5C0FE2032408B0@AD-BR-EX-2.adroot.flemingc.local>
In-Reply-To: <D9B9EB3A112B8F489DFFA00A6D5C0FE2032408B0@AD-BR-EX-2.adroot.flemingc.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Am 30.10.2013 14:15, schrieb Tim Tisdall:

> The problem exists on the other end of the socket; the kernel side.

Do you have tried using gattool to verify that?

Regards,

Alexander Holler