From: Matthias Grimm <joker@cymes.de>
To: "Joseph P. Garcia" <jpgarcia@execpc.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: pbbuttons, need some help
Date: Fri, 08 Mar 2002 23:31:21 +0100 [thread overview]
Message-ID: <3C893BB9.6040002@cymes.de> (raw)
In-Reply-To: 20020307134140.56d70400.jpgarcia@execpc.com
Joseph P. Garcia wrote:
Hi,
> The best way to get battery info now is to use to use /proc/pmu/ in newer
> (2.4) kernels. My gkrellm-pmu plugin used to use adb directly, then PMUD,
> now /proc/pmu/. I had to poke and prod at Paul Mackerras' Batmon to figure
> out O'Hare. But /proc/pmu is transparent to what kind of system its on.
> Divide and conquer. Nice that another conduit thats system independant
> exists.
Yes, you are right. Why do something again what's already done. I looked
into the kernel source, afterwards into PMUD and then I thought that's
the way and other possibilities didn't come into my mind although I knew
/proc/pmu. So I will borrow some code from gkrellm-pmu for that task. ;-)
> Along those same lines, I have a sugesstion for the gtk client for
> pbbuttons. The program should use the X keycodes rather than associate
> with the daemon that controls the hardware. This serves two purposes: X
> handles any client/server mess, and the GUI will be the system independant
> figurehead it should be (IMO). Bastien wrote a similar program that uses
> the keycodes, so it could be used on any system with the keys, even an x86.
> (hadess.net)
I didn't understand excactly what you mean. The GTK client is only a
simple stupid program that will do what it's told from the server. It
hasn't any own input routines except the message queue where the
messages from the server arrive. It doesn't get in contact with any
keycodes, neither from X nor from terminal.
What do you mean with 'client/server mess'? I don't use the X-protokoll
for communication and I don't think it would make much sense. We would
hardly benefit from the X-protokoll because the network transparency
isn't needed here. We only want to make the handling of our machines
more comfortable. Or have I misunderstood you here?
> Hope this helps.
Discussions will always help :-) Who else would turn me arround 180
degrees in a blind alley ;-)
Matthias
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-08 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C852E12.3030300@cymes.de>
[not found] ` <20020306090814.15511@mailhost.mipsys.com>
2002-03-07 18:51 ` pbbuttons, need some help Matthias Grimm
2002-03-07 19:41 ` Joseph P. Garcia
2002-03-08 12:33 ` benh
2002-03-08 22:40 ` Matthias Grimm
2002-03-08 22:31 ` Matthias Grimm [this message]
2002-03-09 14:43 ` Tuomas Kuosmanen
2002-03-09 18:25 ` Joseph P. Garcia
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=3C893BB9.6040002@cymes.de \
--to=joker@cymes.de \
--cc=jpgarcia@execpc.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).