From: Catalin Drula <catalin.drula@imag.fr>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Host to Host Controller flow control
Date: Fri, 25 Mar 2005 12:01:18 +0000 (UTC) [thread overview]
Message-ID: <loom.20050325T125759-162@post.gmane.org> (raw)
In-Reply-To: 1111751283.9195.60.camel@pegasus
Hi Marcel,
Marcel Holtmann <marcel <at> holtmann.org> writes:
> the host to host controller flow control means that we tell the chip to
> use flow control. This is the other way around and we don't support it
> at the moment, because it is easy for us to handle big packets. If you
> enable host to host controller flow control you need to tell the chip
> when you are ready to receive more packets.
Ok, but I think what we are missing then is called "host controller to host flow
control" or as in the specification "flow control... in the direction from the
Host Controller to the Host". Even the command that enables this is called
Set_Host_Controller_To_Host_Flow_Control.
Correct me if I am wrong, but I think you should update the TODO list to say
* Host Controller to Host flow control
Catalin
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-25 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 17:04 [Bluez-devel] Host to Host Controller flow control Catalin Drula
2005-03-25 9:11 ` [Bluez-devel] " Catalin Drula
2005-03-25 11:48 ` Marcel Holtmann
2005-03-25 12:01 ` Catalin Drula [this message]
2005-03-25 12:27 ` 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=loom.20050325T125759-162@post.gmane.org \
--to=catalin.drula@imag.fr \
--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