From: Mauro Tortonesi <mtortonesi@ing.unife.it>
To: jt@hpl.hp.com, Jean Tourrilhes <jt@bougret.hpl.hp.com>
Cc: BlueZ mailing list <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: bluez & qos
Date: Thu, 5 Feb 2004 11:46:55 +0100 [thread overview]
Message-ID: <200402051146.55939.mtortonesi@ing.unife.it> (raw)
In-Reply-To: <20040204174648.GA16590@bougret.hpl.hp.com>
On Wednesday 04 February 2004 18:46, Jean Tourrilhes wrote:
> On Wed, Feb 04, 2004 at 12:23:29PM +0100, Mauro Tortonesi wrote:
> > hi to everybody,
> >
> > i was trying to do some qos setup tests with bluez and i have seen that
> > there is barely no qos support in bluez. it would be nice to develop an
> > ioctl(2)-based extension to set up qos on bluez sockets. i have just
> > started working on the code. marcel, would you be intested in having qos
> > support for bluez?
> >
> > BTW: i have seen that Jean Tourrilhes (included in cc) has been working
> > on qos with CSR chips a while ago. jean, since i have seen no
> > announcements on this list i suppose that you haven't production-quality
> > code adding qos support for bluez...
>
> My code just open a HCI socket and send HCI commands. The HCI
> commands are pretty straightforward, well documented and do everything
> you want, so I don't see the point in adding weird ioctls. The main
> issue I have with ioctls is that they are blocking, so that's why my
> code use HCI socket for everything (including Inquiry).
i think the "open a HCI socket and send HCI commands" approach (which indeed
has many advantages) is a bit too low-level to be used in standard
applications as a way for setting QoS over Bluez.
since QoS is semantically an attribute of a connection, it would be nice to
have ioctl(2) commands for setting QoS parameters on a given connection.
> Not that the main issue will be firware support. For example
> the QoS feature I needed is not implemented in the CSR firmware.
do you mean that most of the firmware of the Bluetooth chips in commerce do
not support/implement HCI QoS commands (such as OGF 0x0002 OCF 0x0007)? what
version of CSR firmware are you talking about?
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi mtortonesi@ing.unife.it
mauro@deepspace6.net
mauro@ferrara.linux.it
Deep Space 6 - IPv6 with Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-05 10:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 1:58 L2CAP non-blocking socket nasty race conditions Jean Tourrilhes
2004-02-04 7:17 ` [Bluez-devel] " Marcel Holtmann
2004-02-04 17:58 ` Jean Tourrilhes
2004-02-04 19:58 ` [Bluez-devel] " Marcel Holtmann
2004-02-04 21:45 ` Jean Tourrilhes
2004-02-05 1:00 ` [Bluez-devel] " Marcel Holtmann
2004-02-05 1:11 ` Jean Tourrilhes
2004-02-05 1:30 ` [Bluez-devel] " Marcel Holtmann
2004-02-05 1:40 ` Jean Tourrilhes
2004-02-05 2:21 ` [Bluez-devel] " Marcel Holtmann
2004-02-05 2:26 ` Jean Tourrilhes
2004-02-05 2:36 ` [Bluez-devel] " Marcel Holtmann
2004-02-05 2:42 ` Jean Tourrilhes
2004-02-05 3:30 ` Jean Tourrilhes
2004-02-05 13:49 ` [Bluez-devel] " Marcel Holtmann
2004-02-05 17:19 ` Jean Tourrilhes
2004-02-05 18:17 ` [Bluez-devel] " Marcel Holtmann
2004-02-05 23:13 ` Jean Tourrilhes
2004-02-05 23:37 ` [Bluez-devel] " Marcel Holtmann
2004-02-05 23:43 ` Jean Tourrilhes
2004-02-04 11:23 ` [Bluez-devel] bluez & qos Mauro Tortonesi
2004-02-04 11:36 ` Marcel Holtmann
2004-02-04 17:46 ` [Bluez-devel] " Jean Tourrilhes
2004-02-05 10:46 ` Mauro Tortonesi [this message]
2004-02-05 17:22 ` Jean Tourrilhes
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=200402051146.55939.mtortonesi@ing.unife.it \
--to=mtortonesi@ing.unife.it \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.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