From: Andrew Morton <akpm@linux-foundation.org>
To: spock@gentoo.org
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] fbdev: make fb_find_mode look for a mode with the highest refresh rate
Date: Sat, 23 Jun 2007 11:04:24 -0700 [thread overview]
Message-ID: <20070623110424.9a68d82d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070623105046.GB12623@spock.one.pl>
On Sat, 23 Jun 2007 12:50:46 +0200 Michal Januszewski <spock@gentoo.org> wrote:
> If the refresh rate hasn't been explicitly specified, fd_find_mode
> currently returns the first mode with the requested resolution. Change
> it so that it returns a mode with the requested resolution and the
> highest refresh rate.
>
> Also export fb_destroy_modelist, which is used in uvesafb.
>
> Signed-off-by: Michal Januszewski <spock@gentoo.org>
> ---
> drivers/video/modedb.c | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c
> index 3741ad7..98ee77b 100644
> --- a/drivers/video/modedb.c
> +++ b/drivers/video/modedb.c
> @@ -606,16 +606,18 @@ done:
> DPRINTK("Trying specified video mode%s %ix%i\n",
> refresh_specified ? "" : " (ignoring refresh rate)", xres, yres);
>
> + if (!refresh_specified)
> + refresh = 200;
> diff = refresh;
> best = -1;
> for (i = 0; i < dbsize; i++) {
> if (name_matches(db[i], name, namelen) ||
> (res_specified && res_matches(db[i], xres, yres))) {
> if(!fb_try_mode(var, info, &db[i], bpp)) {
> - if(!refresh_specified || db[i].refresh == refresh)
> + if (refresh_specified && db[i].refresh == refresh)
> return 1;
> else {
> - if(diff > abs(db[i].refresh - refresh)) {
> + if (diff > abs(db[i].refresh - refresh)) {
> diff = abs(db[i].refresh - refresh);
> best = i;
> }
> @@ -938,6 +940,7 @@ void fb_destroy_modelist(struct list_head *head)
> kfree(pos);
> }
> }
> +EXPORT_SYMBOL_GPL(fb_destroy_modelist);
>
fbdev ignoramus asks: isn't this pretty risky? People who were previously
relying upon (or at least using) the kernel's default resolution will find
their displays coming up in a quite different resolution.
This change seems to be quite unrelated to the uvesafb stuff and should be
in a separate patch from the export, which _is_ uvesafb-related. I think.
If that's wrong then the changelog could do with some attention.
next prev parent reply other threads:[~2007-06-23 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 10:50 [PATCH 1/4] fbdev: make fb_find_mode look for a mode with the highest refresh rate Michal Januszewski
2007-06-23 10:50 ` Michal Januszewski
2007-06-23 18:04 ` Andrew Morton [this message]
2007-06-23 21:26 ` Michal Januszewski
2007-06-23 21:26 ` Michal Januszewski
2007-07-12 8:34 ` Antonino A. Daplas
2007-07-12 8:34 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-07-12 8:31 ` Antonino A. Daplas
2007-07-12 8:31 ` [Linux-fbdev-devel] " Antonino A. Daplas
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=20070623110424.9a68d82d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@gentoo.org \
/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.