All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
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
Date: Wed, 30 Oct 2013 15:16:04 +0100	[thread overview]
Message-ID: <527114A4.5010207@ahsoftware.de> (raw)
In-Reply-To: <D9B9EB3A112B8F489DFFA00A6D5C0FE2032408B0@AD-BR-EX-2.adroot.flemingc.local>

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


  reply	other threads:[~2013-10-30 14:16 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 [this message]
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
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=527114A4.5010207@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=linux-bluetooth@vger.kernel.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.