From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Re: Bluetooth SCO message sending (sco_send_frame)
Date: Fri, 26 Aug 2005 21:11:37 -0600 [thread overview]
Message-ID: <430FD9E9.3030604@xmission.com> (raw)
In-Reply-To: <430E9192.1010609@core.kaist.ac.kr>
Youngwoo
> I used the "btsco" program.
> Do you think that "btsco' program is changed to solve my problem?
>
> I think btsco program read data from bluetooth h4 device, and just write
> data to bluetooth.
> Also, Application has no information about socket and MTU size.
> Is it hard to handling data fragmentation in application program?
>
> I think framgmentation is handled by kernel if we need.
> Otherwise h4 device driver must guarantee that data frame size is
> smaller than MTU.
When does this fragmentation problem show up? btsco is not doing
anything special so we expect the kernel to take care of it...
Brad
-------------------------------------------------------
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 prev parent reply other threads:[~2005-08-27 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 3:50 [Bluez-devel] Re: Re: Bluetooth SCO message sending (sco_send_frame) Youngwoo Park
2005-08-27 3:11 ` Brad Midgley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 3:35 Young-woo Park
2005-08-25 19:11 ` Marcel Holtmann
2005-08-24 5:45 Youngwoo Park
2005-08-24 9:56 ` 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=430FD9E9.3030604@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