From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Re: Framebuffer console not working with matroxfb on 2.6
Date: Fri, 17 Sep 2004 19:21:50 +0800 [thread overview]
Message-ID: <200409171921.50273.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0409171151540.19914@waterleaf.sonytel.be>
On Friday 17 September 2004 17:53, Geert Uytterhoeven wrote:
> On Fri, 17 Sep 2004, Michal 'hramrach' Suchanek wrote:
> > However, I still get a minor problem with the driver.
> > When I switch between the default 640x480-60 mode and 1024x768-85 mode
> > the 1024x768 gets interlaced, with completely different timings. I have
> > to use fbset to restore it to 1024x768-85.
>
> I think this is a `feature' of the new mode selection code. When I tried
> booting my Radeon with `1024x768@100', I got 87 Hz interlaced...
>
Michal's problem is more of a failure to preserve the per-display var, which
should be fixed with recent mm or rc kernels.
Yours is more of boot mode selection problem and most drivers use
fb_find_mode() for that. The default modedb does not have 1024x768@100
non-interlaced, so it passed the interlaced version to the driver, which it
happily accepted. Thus, you get the interlaced version.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next prev parent reply other threads:[~2004-09-17 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 12:04 Framebuffer console not working with matroxfb on 2.6 Petr Vandrovec
2004-09-17 8:51 ` Michal 'hramrach' Suchanek
2004-09-17 9:53 ` Geert Uytterhoeven
2004-09-17 11:21 ` Antonino A. Daplas [this message]
2004-09-17 11:50 ` Geert Uytterhoeven
2004-09-17 13:38 ` Antonino A. Daplas
2004-09-26 8:29 ` Benjamin Herrenschmidt
2004-09-17 11:07 ` 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=200409171921.50273.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).