From: Marcel Holtmann <marcel@holtmann.org>
To: Aaron Klish <aklish1@urbana.css.mot.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RFCOMM TTY data loss
Date: 21 Oct 2003 14:09:05 +0200 [thread overview]
Message-ID: <1066738150.1005.119.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.20.0310141004130.13019-100000@wombat.urbana.css.mot.com>
Hi Aaron,
> There seems to be a problem between the Rfcomm tty driver code
> and the generic n_tty line discipline where data can be lost.
please tell us which kernel version you have tested. Have you used any
additional patches that we should know of? We included a TTY buffer
management patch from David Woodhouse some time ago.
Do you have a test program with that we can reproduce this behaviour?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-10-21 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 21:51 [Bluez-devel] RFCOMM TTY data loss Aaron Klish
2003-10-21 12:09 ` Marcel Holtmann [this message]
2003-10-22 15:17 ` Aaron Klish
2003-10-22 15:51 ` Aaron Klish
2003-10-23 6:03 ` Marcel Holtmann
2003-10-23 22:08 ` setsockopt for RFCOMM Aaron Klish
2003-10-24 6:24 ` [Bluez-devel] " 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=1066738150.1005.119.camel@pegasus \
--to=marcel@holtmann.org \
--cc=aklish1@urbana.css.mot.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