From: Simone Crippa <simone.crippa@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] apple wireless keyboard
Date: Fri, 11 Jun 2004 20:44:11 +0200 [thread overview]
Message-ID: <40C9FD7B.6000004@gmx.net> (raw)
Hello list,
I bought a shiny new Apple Wireless Keyboard last week because I like to
type on a "big" keyboard using my laptop, but I "hate" tethers!!!
Before buying it I quickly looked in the net to discover that it is
indeed possible. After a deeper search for some information I discovered
that it is not a very well documented task (either Google_Groups,
Newsgroups, ...).
I found _some_ information on this list some weeks ago, but it didn't
really help me a lot. So I thought, I might contact Marcel Holtmann
directly, who seems to know quite a bit about it :-)
But since I don't want to bother him with my simple questions, I thought
maybe someone very, very kind on this list might have faced my same
problems before ... :-)
What I have:
- Apple Keyboard
- HP nx7000 laptop with built-in Bluetooth
- bluez-utils + libs 2.7 (Debian unstable)
- hidp module from mh3 patch on 2.6.6 kernel
What works so far:
- PIN authentification (othewise no info!!)
- synchronisation over Bluetooth with Palm (so, Bluetooth connection
works!)
- hcitool info <BD-keyboard> (gives out lots of funny HW info! ...
"Broadcom Corp."???)
- Palm finds Apple Keyboard (so, Bluetooth in keyboard works)
What does not work:
- hidd -s give out either:
Searching ...
Connecting to device 00:0A:95:39:67:0F
Can't create HID control channel: Host is down
or:
Connecting to device 00:0A:95:39:67:0F
Can't create HID control channel: Device or resource busy
or:
No devices in range or visible
not in that order, pick what you prefer ... which is kind of funny,
since I touch nothing on the keyboard and the output changes continuosly.
I tried to look at "hcidump -x" for some info ... but I cannot find a
clue! (btw: thanks to Marcel ... "hcidump -x" helped me for the PIN-auth
problem!!!)
Thanks for your patience, Simone
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-06-11 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 18:44 Simone Crippa [this message]
2004-06-14 12:31 ` [Bluez-users] apple wireless keyboard Collin R. Mulliner
2004-06-14 23:29 ` Marcel Holtmann
2004-06-14 16:16 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 4:07 [Bluez-users] Apple Wireless Keyboard William Voorhees
2006-07-12 23:27 ` Marcel Holtmann
2008-04-22 14:58 [Bluez-users] Apple wireless keyboard Phil Endecott
2008-04-22 15:13 ` Odysseus Flappington
2008-04-23 19:04 ` Phil Endecott
2008-04-23 19:50 ` Odysseus Flappington
2008-04-24 15:32 ` Phil Endecott
2008-04-23 17:25 ` Johan Hedberg
2008-04-24 15:49 ` Phil Endecott
2008-04-24 17:29 ` Johan Hedberg
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=40C9FD7B.6000004@gmx.net \
--to=simone.crippa@gmx.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 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.