[Bluez-devel] Bluetooth and HAL

[Bluez-devel] Bluetooth and HAL

[Paul Ionescu]

Hi,

I want to add bluetooth devices in HAL (Hardware Abstraction Layer).
This way all programs interesting in bluetooth devices can be notified of
the addition or removal of a bluetooth device.
What should we export about a bluetooth device that might be
of interest for userspace programs ?
I think of the following, but I don't know if we really need all of them:

bluetooth.address	string (ex: 00:0d:33:44:33:c6)
bluetooth.interface	string  (ex: hci0)
bluetooth.interface_up	int
bluetooth.linux.driver	string   (ex: hci_usb)
bluetooth.linux.ifindex		int
bluetooth.linux.sysfs_path	string
bluetooth.HCI_version		int
bluetooth.HCI_revision		int
bluetooth.LMP_version		int
bluetooth.LMP_version		int
bluetooth.Manufacturer	string
bluetooth.ChipVersion	string
Maybe :
bluetooth.features	?
bluetooth.packet_types	?

Corrections, comments and suggestions are appreciate.

Thanks,
Paul



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Bluetooth and HAL

[Marcel Holtmann]

Hi Paul,

> I want to add bluetooth devices in HAL (Hardware Abstraction Layer).
> This way all programs interesting in bluetooth devices can be notified of
> the addition or removal of a bluetooth device.
> What should we export about a bluetooth device that might be
> of interest for userspace programs ?
> I think of the following, but I don't know if we really need all of them:
> 
> bluetooth.address	string (ex: 00:0d:33:44:33:c6)
> bluetooth.interface	string  (ex: hci0)
> bluetooth.interface_up	int
> bluetooth.linux.driver	string   (ex: hci_usb)
> bluetooth.linux.ifindex		int
> bluetooth.linux.sysfs_path	string
> bluetooth.HCI_version		int
> bluetooth.HCI_revision		int
> bluetooth.LMP_version		int
> bluetooth.LMP_version		int
> bluetooth.Manufacturer	string
> bluetooth.ChipVersion	string
> Maybe :
> bluetooth.features	?
> bluetooth.packet_types	?
> 
> Corrections, comments and suggestions are appreciate.

looks fine so far, but ChipVersion is vendor specific and not really of
interest. For interface_up you may should simply take all flags and then
the userspace application can decode it like hciconfig does. You may
wanna include the features, but be aware of the extended features from
the Bluetooth 1.2 specification. The packet_types are useless and I am
going to remove that support at some point. Maybe you wanna add the
class of device value.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] Re: Bluetooth and HAL

[Paul Ionescu]

Hi Marcel,

I'll remove the ChipVersion then, and I have some more questions:
How do we tell if we have a BT 1.0 or BT 1.1 or BT 1.2  adapter ?
By looking at HCI and LMP numbers ?
Do we need a separate bluetooth.version too ?
Do end user programs really need HCI and LMP version/revision ?


Thanks,
Paul

On Thu, 20 Jan 2005 01:26:25 +0100, Marcel Holtmann wrote:

> Hi Paul,
> 
>> I want to add bluetooth devices in HAL (Hardware Abstraction Layer).
>> This way all programs interesting in bluetooth devices can be notified
>> of the addition or removal of a bluetooth device. What should we export
>> about a bluetooth device that might be of interest for userspace
>> programs ?
>> I think of the following, but I don't know if we really need all of
>> them:
>> 
>> bluetooth.address	string (ex: 00:0d:33:44:33:c6) bluetooth.interface
>> string  (ex: hci0) bluetooth.interface_up	int
>> bluetooth.linux.driver	string   (ex: hci_usb) bluetooth.linux.ifindex	
>> int
>> bluetooth.linux.sysfs_path	string
>> bluetooth.HCI_version		int
>> bluetooth.HCI_revision		int
>> bluetooth.LMP_version		int
>> bluetooth.LMP_version		int
>> bluetooth.Manufacturer	string
>> bluetooth.ChipVersion	string
>> Maybe :
>> bluetooth.features	?
>> bluetooth.packet_types	?
>> 
>> Corrections, comments and suggestions are appreciate.
> 
> looks fine so far, but ChipVersion is vendor specific and not really of
> interest. For interface_up you may should simply take all flags and then
> the userspace application can decode it like hciconfig does. You may wanna
> include the features, but be aware of the extended features from the
> Bluetooth 1.2 specification. The packet_types are useless and I am going
> to remove that support at some point. Maybe you wanna add the class of
> device value.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> ------------------------------------------------------- This SF.Net email
> is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source
> databases. Create drag-&-drop reports. Save time by over 75%! Publish
> reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at
> http://www.intelliview.com/go/osdn_nl




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Re: Bluetooth and HAL

[Marcel Holtmann]

Hi Paul,

> I'll remove the ChipVersion then, and I have some more questions:
> How do we tell if we have a BT 1.0 or BT 1.1 or BT 1.2  adapter ?
> By looking at HCI and LMP numbers ?

it is the HCI_version and LMP_version. They can be different, but in
general they show the same version of the specification.

> Do we need a separate bluetooth.version too ?

No.

> Do end user programs really need HCI and LMP version/revision ?

Only if they wanna display some information about the device. Otherwise
they are useless, because the kernel or the Bluetooth library will hide
the differences.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel