From: Ian Gulliver <ian@penguinhosting.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Apple keyboard problem
Date: Sun, 9 Jan 2005 18:58:04 -0500 [thread overview]
Message-ID: <20050109235803.GC5291@penguinhosting.net> (raw)
In-Reply-To: <1105324578.8637.8.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
> > I never get a PIN entry request (as I did with the mouse) or any other
> > error. There's a long pause between the "Connecting to device" and the
> > "Can't create". According to lib.c in the kernel, ENOSYS is returned
> > on an unrecognized error code, but I don't know enough about the packet
> > formats to figure out what byte is the error code, or what else it might
> > mean. Attached is an hcidump during the "hidd --search" run.
>
> at that pause you should type a numeric PIN on your keyboard and then
> press return.
Sorry, wasn't clear enough. When I'm running in X, the PIN dialog pops
up as expected for the mouse, and not for the keyboard. The blocking
call for that pause from hidd, according to strace, is:
bind(4, {sa_family=AF_BLUETOOTH, sa_data="\0\0\212\323\4\241\16\0\0\0\0\0\0\0"}, 10) = 0
setsockopt(4, SOL_TCP, TCP_NODELAY, "0\0000\0\377\377", 6) = 0
connect(4, {sa_family=AF_BLUETOOTH, sa_data="\21\0\34N:\225\n\0\0\0\0\0\0\0"}, 10
(pause is here)
= -1 ENOSYS (Function not implemented)
Typing a PIN in that space simply causes the expected:
sheba% 0000
zsh: command not found: 0000
:)
--
Ian Gulliver
Penguin Hosting
"Failure is not an option; it comes bundled with your Microsoft products."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-09 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 21:23 [Bluez-users] Apple keyboard problem Ian Gulliver
2005-01-10 2:36 ` Marcel Holtmann
2005-01-09 23:58 ` Ian Gulliver [this message]
2005-01-10 4:05 ` 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=20050109235803.GC5291@penguinhosting.net \
--to=ian@penguinhosting.net \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox