From: Paul Ionescu <i_p_a_u_l@yahoo.com>
To: bluez-devel@lists.sourceforge.net
Cc: hal@freedesktop.org
Subject: [Bluez-devel] Re: Bluetooth and HAL
Date: Thu, 20 Jan 2005 10:17:49 +0200 [thread overview]
Message-ID: <pan.2005.01.20.08.17.45.630346@yahoo.com> (raw)
In-Reply-To: 1106180785.8190.151.camel@pegasus
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
next prev parent reply other threads:[~2005-01-20 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 22:54 [Bluez-devel] Bluetooth and HAL Paul Ionescu
2005-01-20 0:26 ` Marcel Holtmann
2005-01-20 8:17 ` Paul Ionescu [this message]
2005-01-20 12:50 ` [Bluez-devel] " 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=pan.2005.01.20.08.17.45.630346@yahoo.com \
--to=i_p_a_u_l@yahoo.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=hal@freedesktop.org \
/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