On Fri, Jul 22, 2005 at 10:25:24AM -0500, Clark Williams wrote: > /me goes and actually *looks* at the acpi driver(s) Ok. I see! :) > I would recommend writing a completely separate driver that just > provides the hook(s) to get to battery and any other info you want to > provide. I did it on another platform (can't seem to find that code > though) mainly to use the /proc/acpi/event interface and receive button > presses and things like that. Something like a fake-acpi.c that various > platform folks could use to translate their events into the acpi > interface. Yes, just file «arch/arm/kernel/apm.c» does regarding APM. > That's kinda hokey now that I actually wrote it down and looked at it. > Maybe what we need to do is put together a framework somewhat like the > way acpi presents state information, but not called acpi (wouldn't want > someone thinking that we'd ported the acpi interpreter to MIPS :). I'm > not even sure if it should go into /proc or /sys. > > I just liked the fact that the event interface and the status interfaces > were presented in somewhat logical fashion to user space, such that a > shell script could be used to gather information or manipulate the state > (e.g. 'echo 3 >/proc/acpi/sleep' to suspend to RAM). Yes. > Gah. Sorry, you were asking for an answer and I turned this into a > design discussion. My opinion: if you're in a hurry, write a simple Nonono. It's very interesting what you are saying! > driver that presents a /proc interface to get to battery information. Ok. Currently I have some time to spend on it... do you have any suggestions about I can start developing it in the good way? :) Thanks a lot, Rodolfo -- GNU/Linux Solutions e-mail: giometti@xxxxxxxx Linux Device Driver giometti@xxxxxxxxxxxx Embedded Systems home page: giometti.enneenne.com UNIX programming phone: +39 349 2432127
Attachment:
signature.asc
Description: Digital signature
