From: Michal Januszewski <spock@gentoo.org> Date: 2008-01-27 11:35:27
From: Michal Januszewski <spock@gentoo.org>
Don't treat valid modes returned by fb_find_mode() (best-fit modes,
default modes or the first valid mode) as errors.
Signed-off-by: Michal Januszewski <spock@gentoo.org>
---
From: Andrew Morton <akpm@linux-foundation.org> Date: 2008-03-06 06:55:09
On Sun, 27 Jan 2008 12:34:56 +0100 Michal Januszewski [off-list ref] wrote:
From: Michal Januszewski <spock@gentoo.org>
Don't treat valid modes returned by fb_find_mode() (best-fit modes,
default modes or the first valid mode) as errors.
Because I cannot tell what are the consequences of the bug which you're
fixing, hence I cannot tell whether we need this fix in 2.6.25 or even
2.6.24.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
From: Michal Januszewski <spock@gentoo.org> Date: 2008-03-16 11:24:01
From: Michal Januszewski <spock@gentoo.org>
Don't treat valid modes returned by fb_find_mode() (best-fit modes,
default modes or the first valid mode) as errors.
Currently, when fb_find_mode() finds a valid mode belonging to one
of the above-mentioned classes, uvesafb will ignore it and will try
to set a 640x480 video mode. The expected behaviour (introduced by
this patch) would be to use the valid mode returned by fb_find_mode()
instead.
Signed-off-by: Michal Januszewski <spock@gentoo.org>
---
As requested, this patch contains an expanded changelog message. The
bug is by no means critical and should have no impact on the large
majority of users, so it's definitely not 2.6.24 material.