From: Randy Dunlap <rdunlap@xenotime.net>
To: yotam.medini@gmail.com
Cc: linux-kernel@vger.kernel.org, Avery Pennarun <apenwarr@alumnit.ca>
Subject: Re: APM_CONFIG on x86 - Is it possible?
Date: Fri, 31 Dec 2010 14:23:35 -0800 [thread overview]
Message-ID: <20101231142335.84e00497.rdunlap@xenotime.net> (raw)
In-Reply-To: <20101231234010.0165f0e8@janini.home>
On Fri, 31 Dec 2010 23:40:10 +0200 Yotam Medini wrote:
> The .config I ended up with does have:
> CONFIG_APM=m
> But no CONFIG_APM_POWER setting,
> When booting the kernel, I don not have /proc/apm.
> I do get:
>
> $ sudo modprobe apm
> FATAL: Error inserting apm
> (/lib/modules/2.6.32.yumax/kernel/arch/x86/kernel/apm.ko): No such device
>
> Please note that
> drivers/power/Makefile:118
> has:
> obj-$(CONFIG_APM_POWER) += apm_power.o
>
> Also the "/proc/apm" is created in
> drivers/char/Makefile:71
> obj-$(CONFIG_APM_EMULATION) += apm-emulation.o
> drivers/char/apm-emulation.c:668-670
Hint: This is not the only place that /proc/apm is created.
> #ifdef CONFIG_PROC_FS
> proc_create("apm", 0, NULL, &apm_proc_fops);
> #endif
> As far as I understand, CONFIG_APM is not sufficient
> for the creation of "/proc/apm".
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
next prev parent reply other threads:[~2010-12-31 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 17:38 Yotam Medini
2010-12-31 18:33 ` Randy Dunlap
2010-12-31 19:28 ` Yotam Medini
2010-12-31 19:39 ` Randy Dunlap
2010-12-31 21:40 ` Yotam Medini
2010-12-31 21:54 ` Avery Pennarun
2010-12-31 22:05 ` Yotam Medini
2010-12-31 22:10 ` Avery Pennarun
2011-01-01 16:25 ` Stephen Rothwell
2010-12-31 22:23 ` Randy Dunlap [this message]
2011-01-02 19:16 ` CONFIG_APM_POWER - still possible? Yotam Medini
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=20101231142335.84e00497.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=apenwarr@alumnit.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=yotam.medini@gmail.com \
/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
all inboxes | Powered by JetHome®