Re: Power management behavior of linux-2.6.14-omap2-v5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 19, 2008 at 6:48 PM, Woodruff, Richard <r-woodruff2@xxxxxx> wrote:
> You are just talking about your logo disappearing (usually tux)?

No not just tux.

If i run tslib (ts_test) and suspend& resume the
board then also the same behavior is happening.
ie. The normal ts_test screen disappears and
blue screen comes.

Also if i do a cat of some image to /dev/fb0 then
the same image disappears after a
suspend&resume cycle, whether this behavior also
linked to console layer?

Or a higher level mechanism (like X server)
is required to save and restore the framebuffer
after a PM cycle or it's the fb driver's responsibility
to do so?

Regards,
Arun C

>
> It has been this way for years if not forever on all Linux systems.
>
> A long while back in 2.4 this bothered me enough that I did fix it in a MV kernel.  This is in effect of the console layer not saving its logo settings.  It is not all that hard to fix.
>
> For a development system having the logo is kind of a nice thing even an advertising tool.  However, probably no one ships a system with it on.
>
> You might send a patch in to console people to fix it.  When I sent a patch to MV long back it was discarded.  I didn't send it to the proper maintainer which could have stuck then.
>
> Regards,
> Richard W.
>
>> -----Original Message-----
>> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-
>> owner@xxxxxxxxxxxxxxx] On Behalf Of arun c
>> Sent: Monday, May 19, 2008 1:49 AM
>> To: linux-omap@xxxxxxxxxxxxxxx
>> Subject: Power management behavior of linux-2.6.14-omap2-v5
>>
>> Hi all,
>>
>> I am using linux-2.6.14-omap2-v5 to test PM on 2430SDP.
>>
>> I did
>>
>> a) cat myimg > /dev/fb0
>>     I can see "myimg" displayed on the lcd
>>
>> b) cat /dev/fb0 > myimg_before_sleep
>>
>> c) echo "mem" > /sys/power/state
>>     Board goes to sleep state.
>>
>> d) After a key press the board awakes and lcd
>>    becomes blue "myimg" is disappeared from
>>    the screen.
>>
>> e) cat /dev/fb0 > myimg_after_wakeup
>>
>>  The two binary files "myimg_before_sleep" and
>> "myimg_after_wakeup" differs each other.
>>
>> Can somebody explain me why such a behavior?
>> Why the lcd fails to display the same image
>> before and after sleeping?
>>
>> Regards,
>> Arun C
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux