From: Mario <mario.temporary@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: btsco with an HP embedded bluetooth adapter
Date: Fri, 10 Feb 2006 14:43:54 +0100 [thread overview]
Message-ID: <495ce9180602100543q4f65bef3p@mail.gmail.com> (raw)
In-Reply-To: <43EB9B59.1010107@xmission.com>
2006/2/9, Brad Midgley <bmidgley@xmission.com>:
> Maybe the mtu is only messed up for adapter->headset traffic.
>
> Did you try this patch?
>
> http://sourceforge.net/mailarchive/message.php?msg_id=3D14450798
I've tried it (but I've to say that I forgot to recompile the
snd-bt-sco module; is it important?) without success. Should I see a
different output of 'hciconfig hci0 revision' with this patch?
root@legolas:~# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:10:C6:59:7A:FC ACL MTU: 377:10 SCO MTU: 16:0
Firmware 2.105 / 97
Is my Broadcom chipset supported or not? :|
If you say that this patch could work, I can try a second time.
Thanks for your reply.
Mario
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-02-10 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 15:45 [Bluez-devel] btsco with an HP embedded bluetooth adapter Mario Temporary
2006-02-08 16:58 ` [Bluez-devel] " Mario Temporary
2006-02-09 19:43 ` Brad Midgley
2006-02-10 13:43 ` Mario [this message]
2006-02-10 15:27 ` Brad Midgley
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=495ce9180602100543q4f65bef3p@mail.gmail.com \
--to=mario.temporary@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).