From: Kyle Rose <krose+bluez@krose.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] AMD64 HID pairing
Date: Thu, 07 Oct 2004 17:49:46 -0400 [thread overview]
Message-ID: <khnr7oa8ah1.fsf@hunter-killer.kendall.corp.akamai.com> (raw)
In-Reply-To: <1097185188.7325.75.camel@pegasus> (Marcel Holtmann's message of "Thu, 07 Oct 2004 23:39:48 +0200")
Marcel Holtmann <marcel@holtmann.org> writes:
> this looks very weird. Especially the switching to the VT.
I guess I wasn't very specific here. I switch to VT because I can't
get to a terminal without a working mouse. :) It has nothing to do
with executing hidd --search from a VT vs. a pty.
> Please try to reproduce it with a 2.6.9-rc3-bk7 kernel.
Will do.
> Is the cradle in HID or in HCI mode?
Uh... this isn't something I've dealt with before. When I installed
bluez on the 32 bit system several months ago, I just turned on HIDP
support and it simply "worked." I didn't realize there were different
modes here. How do I switch the mode? Different module?
FWIW, "hcitool dev" gives "hci0 ...", suggesting it is in hci mode,
which probably isn't right.
> Run "hcidump -X" as root whenever possible so we can see if there are
> wrong things.
My hcidump doesn't recognize -X. This is a new option maybe? I'm
using the one from the Debian AMD64 alioth repository (1.10).
Cheers,
Kyle
next prev parent reply other threads:[~2004-10-07 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 17:07 [Bluez-users] AMD64 HID pairing Kyle Rose
2004-10-07 21:39 ` Marcel Holtmann
2004-10-07 21:49 ` Kyle Rose [this message]
2004-10-07 21:58 ` Marcel Holtmann
2004-10-07 22:07 ` Kyle Rose
2004-10-09 15:04 ` Kyle Rose
2004-10-09 17:21 ` Marcel Holtmann
2004-10-09 19:45 ` Kyle Rose
2004-10-09 22:12 ` Marcel Holtmann
2004-10-10 2:19 ` Kyle Rose
2004-10-10 7:57 ` Marcel Holtmann
2004-10-10 4:00 ` Kyle Rose
2004-10-10 7:58 ` Marcel Holtmann
2004-10-10 22:05 ` Kyle Rose
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=khnr7oa8ah1.fsf@hunter-killer.kendall.corp.akamai.com \
--to=krose+bluez@krose.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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