Linux bluetooth development
 help / color / mirror / Atom feed
From: Terry Hardie <terryh@orcas.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Passive scanning of iBeacons results in a "Data Buffer Overflow"
Date: Sat, 8 Mar 2014 22:25:50 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1403082225030.21384@orcas.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1403072307490.21384@orcas.net>

On Fri, 7 Mar 2014, Terry Hardie wrote:

> I'm having something similar to what Adam is reporting. I'm running on a 
> BeagleBone Black, which uses a TI MUSB controller (I think it's different to 
> the Raspberry Pi USB controller?).

I have just found switching the USB 2 hub for a USB 1.1 hub makes the 
problem go away... Not sure what that proves though...


  reply	other threads:[~2014-03-09  6:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 12:41 Passive scanning of iBeacons results in a "Data Buffer Overflow" Adam Warski
2014-02-28 16:14 ` Anderson Lizardo
2014-03-01  9:34   ` Adam Warski
2014-03-01 19:11     ` Anderson Lizardo
2014-03-02 15:07       ` Adam Warski
2014-03-03 15:27         ` Adam Warski
     [not found]         ` <0BA8DEFD-9E73-4A6A-A9E6-1957634CABF8@warski.org>
2014-03-03 18:02           ` Anderson Lizardo
2014-03-03 21:06             ` Adam Warski
2014-03-03 21:25             ` Adam Warski
2014-03-03 23:07               ` Anderson Lizardo
2014-03-05 20:41                 ` Adam Warski
2014-03-10 13:09                   ` Anderson Lizardo
2014-03-16 19:53                     ` Adam Warski
2014-03-18 14:07                       ` Anderson Lizardo
2014-03-19 23:47                         ` Terry Hardie
2014-04-18  9:59                           ` Adam Warski
2014-03-08  7:19 ` Terry Hardie
2014-03-09  6:25   ` Terry Hardie [this message]
2014-03-10 13:21   ` Anderson Lizardo
2014-03-11  0:54     ` Terry Hardie

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=alpine.DEB.2.02.1403082225030.21384@orcas.net \
    --to=terryh@orcas.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