From: Marcel Holtmann <marcel@holtmann.org>
To: Bernard Mentink <Bernard.Mentink@trimble.co.nz>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Keeping keyboards alive
Date: Mon, 15 Mar 2004 20:37:45 +0100 [thread overview]
Message-ID: <1079379465.4395.7.camel@pegasus> (raw)
In-Reply-To: <8285CB7241FCFC4BB721A6F953F9B35E0F38D8@nzc-ap-xch-01.ap.trimblecorp.net>
Hi Bernard,
> Thanks for the reply. In my situation battery drain is not a concern. I am using the keyboard in a PVR situation, i.e I have
> a MythTV linux box in the lounge and I use the keyboard when I am surfing the net, typically I would turn the keyboard on and use
> it for an hour, having it turn off after 10 mins inactivity is only a slight niggle, not really a problem. Just thought that maybe a polling
> parameter could be passed to bthid for those situations...
>
> (I'd offer the use of my keyboard ... but I'm in New Zealand ;-)
for the Microsoft HID devices I fixed it in my new kernel HIDP code. But
without physical access to the Apple keyboard I can't tell you what's
wrong.
Maybe you should look at the old bthid code from Peter Klausler. I think
it has some polling code.
> By the way, I have cobbed together a startup script which I have in run-level-5 to get everything going on powerup, so that I can just turn
> on the keyboard and connect. However, sometimes it does not boot up all the time .... do you have an example of a script that you use?
I have nothing special.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2004-03-15 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8285CB7241FCFC4BB721A6F953F9B35E0F38D8@nzc-ap-xch-01.ap.trimblecorp.net>
2004-03-15 19:37 ` Marcel Holtmann [this message]
2004-03-14 20:07 [Bluez-devel] Keeping keyboards alive Bernard Mentink
2004-03-15 11:29 ` 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=1079379465.4395.7.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Bernard.Mentink@trimble.co.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox