From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: btsco occasional loud bursts of static
Date: Thu, 02 Feb 2006 22:59:02 -0700 [thread overview]
Message-ID: <43E2F126.9040605@xmission.com> (raw)
In-Reply-To: <43E2BD4E.7060905@purdue.edu>
Chase
> I'd love to hlp in any way I can. I'm not sure where this code is that you
> wrote of. Could you point me in the right direction? Also, I am going to
> need
> some kind of documentation on the sco protocol. Do you know where I
> could find
> these?
This is currently all in the kernel.
In the btsco project, you'll see in kernel/btsco.c where sock_recvmsg()
gets data from the set and is followed immediately by some
AUTO_FIXUP_BYTESHIFT code. This is the workaround for the problem.
The sco generic transport is implemented in the kernel source in
drivers/net/bluetooth/sco.c.
The hardware interaction is in net/bluetooth/hci_{conn,core,event}.c and
I suspect this is where things may need work. This is also where hacks
for broadcom sco would probably end up.
Brad
-------------------------------------------------------
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-03 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 2:17 [Bluez-devel] Re: btsco occasional loud bursts of static Chase Douglas
2006-02-03 5:59 ` Brad Midgley [this message]
2006-02-03 15:38 ` 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=43E2F126.9040605@xmission.com \
--to=bmidgley@xmission.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).