Linux bluetooth development
 help / color / mirror / Atom feed
From: "Daryl Van Vorst" <daryl@wideray.com>
To: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Qualification testing - rfcomm
Date: Tue, 27 May 2003 17:17:41 -0700	[thread overview]
Message-ID: <001d01c324ae$8e0d6da0$1a01010a@baked> (raw)

Marcel,

Looks like there were two problems related to xon/xoff (and maybe other
parameters) in the rfcomm_recv_rpn() function.

Here's what's happening: (Please excuse me if I'm slightly off on the
terminology)
 1.  The tester sends a parameter negotiation packet with valid settings an=
d
all bits in the mask set.
 2.  We send back a response with the XON bit in the mask still set
(indicating that we liked it), but the XON_CHAR field is set to 0. We're
supposed to reply with the valid XON character.

I just took a quick look at the code and it appears that if we like the
value then xon_char is left as the default value of 0, and then sent as suc=
h
at the bottom of the function.

And, yes, we have hcidump -w logs (just not yet at my fingertips to send
you). I'll forward them as soon as I get them.

-Daryl.




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2003-05-28  0:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  0:17 Daryl Van Vorst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-08 18:16 Qualification testing - rfcomm Daryl Van Vorst
2003-07-08 21:47 ` [Bluez-devel] " James Courtier-Dutton
2003-07-08 23:23   ` Daryl Van Vorst
2003-07-18 19:35     ` James Courtier-Dutton
2003-07-18 19:30 ` James Courtier-Dutton
2003-07-18 20:25   ` Daryl Van Vorst

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='001d01c324ae$8e0d6da0$1a01010a@baked' \
    --to=daryl@wideray.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