From: "Daryl Van Vorst" <daryl@wideray.com>
To: "'Marcel Holtmann'" <marcel@rvs.uni-bielefeld.de>,
"'Max Krasnyansky'" <maxk@qualcomm.com>
Cc: "'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] RE: Rfcomm qualification
Date: Mon, 11 Aug 2003 09:43:52 -0700 [thread overview]
Message-ID: <000c01c36027$bfdfc490$1a01010a@baked> (raw)
In-Reply-To: <1060121068.962.15.camel@pegasus>
Marcel,
Have you two worked out a solution for this one (see message below)?
Should I use the last patch you sent to test?
-Daryl.
> -----Original Message-----
> From: Marcel Holtmann [mailto:marcel@rvs.uni-bielefeld.de]
> Sent: August 5, 2003 3:04 PM
> To: Max Krasnyansky
> Cc: Daryl Van Vorst; BlueZ Mailing List
> Subject: Re: [Bluez-devel] RE: Rfcomm qualification
>
>
> Hi Max,
>
> > >The attached patch sets the default values for session and dlc
> > >credits to zero and put in RFCOMM_MAX_CREDITS only if we
> receive a PN
> > >with 1.1 flow control.
> > >
> > >What do you think?
> >
> > I don't like this:
> >
> > @@ -746,7 +746,7 @@
> > pn->ack_timer = 0;
> > pn->max_retrans = 0;
> >
> > - if (d->credits) {
> > + if (cr || d->credits) {
> >
> >
> > This basically means that we'll always request CFC even if
> the other
> > side explicitly told us that they don't support it. Which is kinda
> > dumb :).
>
> I know exactly what you mean and I don't like it either. But
> my general purpose of this patch was not to introduce another
> "state" of credits. And btw. credits is a uint at the moment.
>
> What do you thing about using session->flags and once we
> received a positive CFC acknowledgment we set a session wide flag?
>
> > Here is what I would do (no time for the patch sory).
> > When session is created set s->credits to -1. Replace above if()
> > statement
> > with
> > if (s->credits < 0) {
>
> I think only
>
> if (s->credits != 0) {
>
> will work in this case ;)
>
> > Also rfcomm_apply_pn() needs to set d->credits only once at
> the end of
> > the function.
>
> This depends on how strict we want to go with the RFCOMM
> spec. It says that if one dlc requests CFC all other dlc's
> should go with CFC, too. I like to give the dlc the chance to
> deactivate or activate CFC even if session default CFC
> setting says otherwise. But maybe this feature is non-sense -
> I have to think about it in more detail.
>
> Regards
>
> Marcel
>
>
>
next prev parent reply other threads:[~2003-08-11 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 20:58 Rfcomm qualification Daryl Van Vorst
2003-07-29 23:03 ` [Bluez-devel] " Marcel Holtmann
2003-07-30 16:25 ` Daryl Van Vorst
2003-07-30 17:22 ` [Bluez-devel] " Marcel Holtmann
2003-07-30 21:43 ` Marcel Holtmann
2003-07-31 0:01 ` Max Krasnyansky
2003-07-31 0:48 ` Marcel Holtmann
2003-08-05 17:10 ` Max Krasnyansky
2003-08-05 22:04 ` Marcel Holtmann
2003-08-11 16:43 ` Daryl Van Vorst [this message]
2003-08-11 19:03 ` Marcel Holtmann
2003-08-14 17:39 ` Daryl Van Vorst
2003-08-14 17:48 ` 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='000c01c36027$bfdfc490$1a01010a@baked' \
--to=daryl@wideray.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
--cc=maxk@qualcomm.com \
/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