From: Russ Dill <russ.dill@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org, discussion@beagleboard.org
Subject: btusb+slob
Date: Wed, 11 Mar 2009 15:51:28 -0700 [thread overview]
Message-ID: <f9d2a5e10903111551h428ca9fekea7f6960c7666be9@mail.gmail.com> (raw)
After running into problems with btusb on my OMAP3 (arm) based Beagle
Board, I discovered that switching from SLOB to SLAB causes the
problems to go away. With SLOB:
Scanning ...
05:16:CF:F7:04:20 n/a
00:11:F6:05:79:95 ....R#w
00:1A:8A:DB:E8:3D ....R$w9
00:16:CF:F7:04:20
05:1A:8A:DB:E8:3D n/a
Devices:
hci0 00:00:00:00:A8:AE
Connections:
< ACL 00:11:F6:05:79:95 handle 0 state 5 lm MASTER
With SLAB:
Scanning ...
00:1A:8A:DB:E8:3D SGH-T629
Devices:
hci0 00:1B:DC:0F:A8:AE
Connections:
< ACL 00:11:F6:05:79:95 handle 42 state 1 lm SLAVE
I have not been able to test on other architectures yet to determine
if it is another component in the chain (such as the usb OTG
controller) misbehaving with SLOB. This is with git latest (post
2.6.29-rc7) and a number of OMAP branches.
next reply other threads:[~2009-03-11 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 22:51 Russ Dill [this message]
2009-03-12 6:58 ` [beagleboard] btusb+slob Hunyue Yau
2009-03-12 7:10 ` Russ Dill
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=f9d2a5e10903111551h428ca9fekea7f6960c7666be9@mail.gmail.com \
--to=russ.dill@gmail.com \
--cc=discussion@beagleboard.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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