From: Youngwoo Park <ywpark@core.kaist.ac.kr>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] 2. Re: Re: Re: Bluetooth SCO message sending (sco_send_frame)
Date: Mon, 29 Aug 2005 15:44:13 +0900 [thread overview]
Message-ID: <4312AEBD.4090907@core.kaist.ac.kr> (raw)
In my case, there is some problem when I connect SCO over UART(h4).
When I sent data to h4 interface, h4 make frame and btsco sent that
frame to the SCO channel.
The frame size from h4 interface is varied periodically and somtimes
larger than MTU size so SCO channel drop several frames.
Of course I changed the MTU size using "hciconfig scomtu" command but it
is not effective at all.
Now, I tested the problem using samsung module based on CSR bluecore
chipset.
However, there is no problem if I use SCO over USB because the frame
size from USB is always same & smaller than MTU.
--
Youngwoo Park
M.S. Student
CORE(COmputer engineering REsearch) Lab
Dept. EECS, KAIST, Daejeon 305-701, Korea
Phone: +82-42-869-5425 Fax: +82-42-8695425
e-mail: ywpark@core.kaist.ac.kr
--
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-08-29 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 6:44 Youngwoo Park [this message]
2005-09-05 12:14 ` [Bluez-devel] 2. Re: Re: Re: Bluetooth SCO message sending (sco_send_frame) Marcel Holtmann
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=4312AEBD.4090907@core.kaist.ac.kr \
--to=ywpark@core.kaist.ac.kr \
--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