From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] hid flowchart workup
Date: Sun, 29 Oct 2006 13:46:29 -0700 [thread overview]
Message-ID: <45451325.2050703@xmission.com> (raw)
Hey
Hello from the plane! Just crossed Greenland.
I thought I would work up the HID flowchart while it was still fresh.
Found it's gone a bit cold already. Maybe Albert could pipe in with some
references for example code. Do we need code references for the methods
used before and after dbus changes to hidd?
This is what I pieced together:
1. Enumerate input devices
(is there a better method than scanning /dev/input/ for mouse*? what
about keyboard?)
2. Any present? Skip to end
3. Start hcid and hidd
4. HID -> HCI
(I can't put together from my notes what this HID->HCI step meant...)
5. Tell user to make devices discoverable
6. Enumerate input devices again
7. Inquiry (api details)
8. Connect to mouse (api details)
9. Connect to keyboard (api details)
10. Enumerate devices.
11. No devices present still? Jump to 5.
(Is it no devices or is the test for both keyboard and mouse present?)
Brad
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-10-29 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 20:46 Brad Midgley [this message]
2006-10-30 9:37 ` [Bluez-devel] hid flowchart workup Marcel Holtmann
2006-10-31 18:18 ` Brad Midgley
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=45451325.2050703@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.