linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Sellout Bessie <sellout@beautyisfleeting.com>,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>,
	alevkovich@tut.by, "Antonino A. Daplas" <adaplas@pol.net>
Subject: Re: [Bugme-new] [Bug 9762] New: radeonfb and Xpress 200m 5955
Date: Wed, 16 Jan 2008 16:23:22 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801161622060.7015@anakin> (raw)
In-Reply-To: <20080116015707.4d551245.akpm@linux-foundation.org>

On Wed, 16 Jan 2008, Andrew Morton wrote:
> On Wed, 16 Jan 2008 01:33:25 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=9762
> > 
> >            Summary: radeonfb and Xpress 200m 5955
> >            Product: Drivers
> >            Version: 2.5
> >      KernelVersion: >=2.6.23
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: normal
> >           Priority: P1
> >          Component: Console/Framebuffers
> >         AssignedTo: jsimmons@infradead.org
> >         ReportedBy: alevkovich@tut.by
> > 
> > 
> > Latest working kernel version: 2.6.23
> > Earliest failing kernel version: any
> > Distribution: gentoo
> > Hardware Environment: Radeon XPress 200m 5955
> > Software Environment: 
> > Problem Description: framebuffer is ok only with default parameters only (it is
> > 1280x800-8@60). If parameters are video=radeonfb:1280x800-32@60 then xres, yres
> > and xres_virtual are ok but yres_virtual is 1024. It can be corrected by fbset
> > utility so I think it can be corrected in the driver code also.
> > 
> > Steps to reproduce: video=radeonfb:1280x800-32@60 or
> > video=radeonfb:1280x800-16@60
> 
> damn, another post-2.6.2 regression.
> 
> Does anyone know whether this is likely to be a radeonfb problem or an
> fbdev core problem?

Perhaps

commit 1c5dd170927b1aa8e3a01d43d611b840336cdaf2
Author: Michal Januszewski <spock@gentoo.org>
Date:   Tue Oct 16 01:29:19 2007 -0700

    fbdev: find mode with the highest/safest refresh rate in fb_find_mode()
    
    Currently, if the refresh rate is not specified, fb_find_mode() returns the
    first known video mode with the requested resolution, which provides no
    guarantees wrt the refresh rate.  Change this so that the mode with the
    highest refresh rate is returned when the driver provides a custom video mod
e
    database and the monitor limits, and a mode with the safe 60 Hz refresh rate
    otherwise.

M. alevkovich, can you please try to back out that change?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

-------------------------------------------------------------------------
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/

  reply	other threads:[~2008-01-16 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9762-10286@http.bugzilla.kernel.org/>
2008-01-16  9:57 ` [Bugme-new] [Bug 9762] New: radeonfb and Xpress 200m 5955 Andrew Morton
2008-01-16 15:23   ` Geert Uytterhoeven [this message]
2008-01-16 19:12     ` Andrew Morton
2008-01-16 22:37       ` Rafael J. Wysocki

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=Pine.LNX.4.64.0801161622060.7015@anakin \
    --to=geert@linux-m68k.org \
    --cc=adaplas@pol.net \
    --cc=akpm@linux-foundation.org \
    --cc=alevkovich@tut.by \
    --cc=benh@kernel.crashing.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rjw@sisk.pl \
    --cc=sellout@beautyisfleeting.com \
    /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).