linux-kernel - Apm_emulation and proper suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080221123318.41273a1f.Kristoffer.ericson@gmail.com>
Date:	Thu, 21 Feb 2008 12:33:18 +0100
From:	Kristoffer Ericson <kristoffer.ericson@...il.com>
To:	rpurdie@...nedhand.com, rjw@...k.pl
Cc:	linux-main <linux-kernel@...r.kernel.org>
Subject: Apm_emulation and proper suspend

Greetings,

I'm reworking a couple of apm drivers and for whatever reason it doesn't seem to update my /proc/apm_bios. I was under the impression that it should do that when apm_bios was catted? Currently I have a value that never change. I export my get_power_status.. function properly but doesn't seem to touch it. I noticed that Richard had the extern int (void..apm_get_power) (...) declare an extra time (once in apm-emulation.h and another inside sharpsl.c), is that needed?

Also, is apm the "brains" behind the suspend/resume interactions? By that I mean, should suspend be initiated through apm functions
in order to be proper? I've tried to find examples but the best source of suspend related code is Richards code on sharp machines.

I've understod the proper way to suspend going from apm_request_suspend -> all devices suspend -> ready -> arch specific code -> off.

Best wishes
Kristoffer
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/