All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hid flowchart workup
Date: Tue, 31 Oct 2006 11:18:26 -0700	[thread overview]
Message-ID: <45479372.7060404@xmission.com> (raw)
In-Reply-To: <1162201020.24333.24.camel@localhost>

Marcel

ok... more details worked out and just a couple points missing. I added
details for if the user has a working input device but may want to
connect another bt device. This might be nice early in the install for a
bt mouse for example so keyboard shortcuts don't have to be used for the
whole install.

These are the steps an installer will need to fully install a Linux
desktop using a Bluetooth keyboard and mouse only. Every distribution
needs to implement this kind of workflow in their installer. When the
user is asked a question, it should be easy for them to use just the
keyboard or just the mouse (if only one is present) to answer.

1. Enumerate input devices (scan /sys/class/input), go to 3 if none.
2. Ask user if they need to pair any bluetooth input devices. If no, end.
3. Start hcid and hidd
4. run hid2hci to put any hid mode dongle in hci mode
5. Tell user to make devices discoverable
6. Enumerate input devices again
7. Inquiry (Call org.bluez.Adapter.DiscoverDevices())
8. Connect to mouse (api details)
9. Connect to keyboard (api details)
10. Enumerate devices.
11. No devices present still, including plain usb? Jump to 5.
12. Ask user if any remaining devices need to be paired. If yes, jump to 5
13. (Later) copy pairing info from ramdisk to the root of the new system

I think steps 8 & 9 change as we implement dbus pathways. Before dbus,
it would be done by executing
 hidd --search
but eventually could be dbus signals to hidd to search for each type of
device.

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

      reply	other threads:[~2006-10-31 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 20:46 [Bluez-devel] hid flowchart workup Brad Midgley
2006-10-30  9:37 ` Marcel Holtmann
2006-10-31 18:18   ` Brad Midgley [this message]

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=45479372.7060404@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.