From: Marcel Holtmann <marcel@holtmann.org>
To: Till Harbaum <harbaum@beecon.de>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Small bugfix for hstest
Date: Mon, 30 Aug 2004 18:07:10 +0200 [thread overview]
Message-ID: <1093882030.5620.86.camel@pegasus> (raw)
In-Reply-To: <200408301753.25934.harbaum@beecon.de>
Hi Till,
> i have played around with hstest and some uart based hardware and found a
> problem, that only seems to happen with uart based devices:
>
> A client may receive sco data packets that are bigger than the sco mtu. hstest
> returns packets of exactly the same size of the packets it received. If the
> packet received is bigger then the sco mtu, then packets bigger than sco mtu
> are being sent and being dropped in the kernel. As a result, no data is being
> sent at all. Instead multiple smaller sco packets should be sent.
>
> The attached patch has to be applied to bluez-utils/test/hstest.c and fixes
> the problem inside hstest. It would as well be possible to make the kernel
> sco code detect this and fragment the payload accordingly. But imho this
> should be done in the application.
I applied the patch, but there must be space between "while" and "(" to
keep me and the coding style happy ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-08-30 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 15:53 [Bluez-devel] Small bugfix for hstest Till Harbaum
2004-08-30 16:07 ` 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=1093882030.5620.86.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=harbaum@beecon.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.