All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Re: bluez & qos
Date: Wed, 08 Dec 2004 17:36:22 +0100	[thread overview]
Message-ID: <1102523782.9988.80.camel@pegasus> (raw)
In-Reply-To: <AFE91B59A185A5439840B43AB7919047A83CA5@mchp997a.mch.sbs.de>

Hi Matthias,

> Basically I want to do the same like Jean Tourrilhes two years ago,
> hoping that chips / firmware have better QoS support meanwhile: 
> "... I"m trying to get the latency under control. I"m using BNEP with a mix
> of TCP/IP traffic, ..."
> 
> I searched the mailing archiv for QoS and found a lot of firmware specific
> discussion. 
> 
> What I couldnt find, but what I would need first is a kind of QoS-Howto,
> explaining generally how to realize QoS with Bluez, i.e. how to control the
> maximum poll interval.
> It would be great to have some examplary code, that adjusts
> the poll interval with the HCI_QoS_Setup command or sth. like that.

I don't know of any public example for QoS.

Regards

Marcel




-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-12-08 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 16:29 [Bluez-devel] Re: Re: bluez & qos Kutschenreuter Matthias
2004-12-08 16:36 ` 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=1102523782.9988.80.camel@pegasus \
    --to=marcel@holtmann.org \
    --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 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.