All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 1/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES
Date: Fri, 12 Aug 2011 00:47:25 +0100	[thread overview]
Message-ID: <1313106445.14274.478.camel@rex> (raw)
In-Reply-To: <606861a92864cb728203fdf5db286d684d2537eb.1313090099.git.bruce.ashfield@windriver.com>

On Thu, 2011-08-11 at 15:16 -0400, Bruce Ashfield wrote:
> Fixes [YOCTO: #916]
> 
> apm is not something that we require in our yocto reference beagleboard
> BSP. It currently is listed in the MACHINE_FEATURES for the board, which
> leads to the runtime message:
> 
>   Starting advanced power management daemon: No APM support in kernel
> 
> Since "/proc/apm" is not present. The board config we are targeting does
> not have the hardware to back this, so adding the emulation support
> wouldn't yield useful data. We'll leave this extended functionality for
> other more appropriate beagleboard configs.

On arm it used to be the case that this was the only way to expose user
interface to suspend/resume the machine. Its not so much about their
being hardware present for it as the whole kernel side was emulation of
the user space notification part.

Has something changed in recent kernels in this area?

Cheers,

Richard





  reply	other threads:[~2011-08-11 23:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 19:16 [PATCH 0/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES Bruce Ashfield
2011-08-11 19:16 ` [PATCH 1/1] " Bruce Ashfield
2011-08-11 23:47   ` Richard Purdie [this message]
2011-08-12  0:51     ` Bruce Ashfield
2011-08-12 13:07       ` Richard Purdie
2011-08-12 13:13         ` Bruce Ashfield

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=1313106445.14274.478.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.org \
    --cc=saul.wold@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.