[PATCH 0/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES

[PATCH 0/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES

[Bruce Ashfield]

Richard/Saul,

Just repeating the patch contents here:

[
   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 
]

The following changes since commit 0350be945877b61eb8125663887fd7ed1c3923ab:
  Khem Raj (1):
        scripts/runqemu: Make it run on ubuntu 11.10

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/apm
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/apm

Bruce Ashfield (1):
  meta-yocto: remove apm from beagleboard MACHINE_FEATURES

 meta-yocto/conf/machine/beagleboard.conf |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

[PATCH 1/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES

[Bruce Ashfield]

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.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta-yocto/conf/machine/beagleboard.conf |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/machine/beagleboard.conf b/meta-yocto/conf/machine/beagleboard.conf
index 0b3cebc..fc0ecc7 100644
--- a/meta-yocto/conf/machine/beagleboard.conf
+++ b/meta-yocto/conf/machine/beagleboard.conf
@@ -36,4 +36,4 @@ UBOOT_MACHINE = "omap3_beagle_config"
 UBOOT_ENTRYPOINT = "0x80008000"
 UBOOT_LOADADDRESS = "0x80008000"
 
-MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat alsa"
+MACHINE_FEATURES = "kernel26 usbgadget usbhost vfat alsa"
-- 
1.7.0.4

Re: [PATCH 1/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES

[Richard Purdie]

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

Re: [PATCH 1/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES

[Bruce Ashfield]

On 11-08-11 7:47 PM, Richard Purdie wrote:
> 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?

I won't claim to be an expert here .. but I haven't used apmd
on many machines in quite a while. Assuming suspend_ops is
implemented, it is typically just something ike this:

  echo mem > /sys/power/state

    or

  echo standby > /sys/power/state

With a wakeup via the rtc, or whatever the board offers. I'm
cc'ing Liming on this, since he's been poking at the board recently
and may have more hands on information to share.

If we ARE removing this capability, then we'll take the other option
that we had for this case and enable the emulation.

Cheers,

Bruce




>
> Cheers,
>
> Richard
>
>
>

Re: [PATCH 1/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES

[Richard Purdie]

On Thu, 2011-08-11 at 20:51 -0400, Bruce Ashfield wrote:
> On 11-08-11 7:47 PM, Richard Purdie wrote:
> > 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?
> 
> I won't claim to be an expert here .. but I haven't used apmd
> on many machines in quite a while. Assuming suspend_ops is
> implemented, it is typically just something ike this:
> 
>   echo mem > /sys/power/state
> 
>     or
> 
>   echo standby > /sys/power/state
> 
> With a wakeup via the rtc, or whatever the board offers. I'm
> cc'ing Liming on this, since he's been poking at the board recently
> and may have more hands on information to share.
> 
> If we ARE removing this capability, then we'll take the other option
> that we had for this case and enable the emulation.

I have a suspicion that certain parts of the sato code do
assume /dev/apm_bios device emulation is present to get userspace
notification of suspend/resume events which the above doesn't provide
last I checked.

Likely this isn't an issue and I think that code in sato (matchbox panel
app iirc) is toggled by the MACHINE_FEATURES but its certainly worth
keeping in mind...

Cheers,

Richard

Re: [PATCH 1/1] meta-yocto: remove apm from beagleboard MACHINE_FEATURES

[Bruce Ashfield]

On 11-08-12 09:07 AM, Richard Purdie wrote:
> On Thu, 2011-08-11 at 20:51 -0400, Bruce Ashfield wrote:
>> On 11-08-11 7:47 PM, Richard Purdie wrote:
>>> 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?
>>
>> I won't claim to be an expert here .. but I haven't used apmd
>> on many machines in quite a while. Assuming suspend_ops is
>> implemented, it is typically just something ike this:
>>
>>    echo mem>  /sys/power/state
>>
>>      or
>>
>>    echo standby>  /sys/power/state
>>
>> With a wakeup via the rtc, or whatever the board offers. I'm
>> cc'ing Liming on this, since he's been poking at the board recently
>> and may have more hands on information to share.
>>
>> If we ARE removing this capability, then we'll take the other option
>> that we had for this case and enable the emulation.
>
> I have a suspicion that certain parts of the sato code do
> assume /dev/apm_bios device emulation is present to get userspace
> notification of suspend/resume events which the above doesn't provide
> last I checked.
>
> Likely this isn't an issue and I think that code in sato (matchbox panel
> app iirc) is toggled by the MACHINE_FEATURES but its certainly worth
> keeping in mind...

Ack'd. We'll have a look at this. Drop my current pull
request, and this can stand a deeper look.

Bruce

>
> Cheers,
>
> Richard
>
>
>