From: Matthew Grant <grantma@anathoth.gen.nz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] PROBLEM: Apple Powerbook and apple keyboard, start up sequence fails
Date: Mon, 15 Nov 2004 21:25:35 +1300 [thread overview]
Message-ID: <1100507134.6064.8.camel@localhost> (raw)
In-Reply-To: <1100463431.21403.73.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 2693 bytes --]
On Mon, 2004-11-15 at 09:17, Marcel Holtmann wrote:
> Hi Matthew,
>
> > BT keyboard is connected on startup, but no keyboard output is
> > happening, and capslock light does not turn on when capslock key is
> > pressed. This is not just the connection delay, as my mouse reconnects
> > successfully after boot.
>
No, there are definitely key press events coming through the BT stack.
The debug I sent shows it, and it has been confirmed with more than just
a cursory observation. They are NOT getting into the HID layer. That
is what I want to look at it, after checking correctness of incoming
events and negotiation.
> maybe the keyboard firmware is buggy. I read that Apple has a firmware
> update for their mouse and keyboard and I think it is worth to try it.
That is applied, to this keyboard, and the other one that does not
behave like this.
> Do you run your Bluetooth device in security mode 3?
>
Yes, I do not want to broadcast passwords for everyone to listen to.
Also, I have a second keyboard that does not behave like this...
We won't really know what is going on until things have been examined.
I was after some pointers on where to start looking at the hidp.ko
interface and the connection negotiation with the kernel HID core. This
is obviously the first place to look and check from what has been
observed so far.
> > I believe the Apple Open firmware on the powerbook negotiates a
> > connection with the keyboard on power up or boot, and leaves the
> > built-in CSR USB dongle in USB HID emulation mode. The keyboard starts
> > working after I switch it on and off, and it renegotiates a connection.
> It is all on the CSR BlueCore02 chip. The Apple firmware does nothing.
Thanks for that bit of info.
Regards,
Matthew Grant
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users
--
===============================================================================
Matthew Grant /\ ^/\^ grantma@anathoth.gen.nz /~~~~\
A Linux Network Guy /~~\^/~~\_/~~~~~\_______/~~~~~~~~~~\____/******\
===GPG KeyID: 2EE20270 FingerPrint: 8C2535E1A11DF3EA5EA19125BA4E790E2EE20270==
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-11-15 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 19:36 [Bluez-users] PROBLEM: Apple Powerbook and apple keyboard, start up sequence fails Matthew Grant
2004-11-14 20:17 ` Marcel Holtmann
2004-11-15 8:25 ` Matthew Grant [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=1100507134.6064.8.camel@localhost \
--to=grantma@anathoth.gen.nz \
--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