Re: [Bluez-devel] Re: bluez & qos

[Jean Tourrilhes <jt@bougret.hpl.hp.com>]

On Thu, Feb 05, 2004 at 11:46:55AM +0100, Mauro Tortonesi wrote:
> 
> 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.

	Aggregating the QoS of the various sockets into a generic QoS
that you can pass to the HCI is not a trivial problem. You can not
guarantee that there will only be one socket per handle.

> > 	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?

	No, I'm saying "the QoS feature I *needed*". I want QoS
*events*, most firmware don't support that.

> Mauro Tortonesi

	Ciao.

	Jean


-------------------------------------------------------
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