From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] 2. Re: Re: Re: Bluetooth SCO message sending (sco_send_frame)
Date: Mon, 05 Sep 2005 14:14:07 +0200 [thread overview]
Message-ID: <1125922447.11955.24.camel@pegasus> (raw)
In-Reply-To: <4312AEBD.4090907@core.kaist.ac.kr>
Hi,
> 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.
this command is useless.
> 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.
As I told you, the kernel will tell you the MTU size you have to use and
then you must segment and reassembly in your code.
Regards
Marcel
-------------------------------------------------------
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
prev parent reply other threads:[~2005-09-05 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 6:44 [Bluez-devel] 2. Re: Re: Re: Bluetooth SCO message sending (sco_send_frame) Youngwoo Park
2005-09-05 12:14 ` Marcel Holtmann [this message]
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=1125922447.11955.24.camel@pegasus \
--to=marcel@holtmann.org \
--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