public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Ionescu <i_p_a_u_l@yahoo.com>
To: bluez-devel@lists.sourceforge.net
Cc: hal@freedesktop.org
Subject: [Bluez-devel] Bluetooth and HAL
Date: Thu, 20 Jan 2005 00:54:30 +0200	[thread overview]
Message-ID: <pan.2005.01.19.22.54.29.108027@yahoo.com> (raw)

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

             reply	other threads:[~2005-01-19 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 22:54 Paul Ionescu [this message]
2005-01-20  0:26 ` [Bluez-devel] Bluetooth and HAL Marcel Holtmann
2005-01-20  8:17   ` [Bluez-devel] " Paul Ionescu
2005-01-20 12:50     ` 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.19.22.54.29.108027@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