From: Andrew Morton <akpm@linux-foundation.org>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: nestorac@gmail.com, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-fbdev-devel@lists.sourceforge.net,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 10205] New: BUG: Display gets corrupted when using lxfb driver on a GeodeLX 5535 based chipset
Date: Sun, 9 Mar 2008 11:54:27 -0700 [thread overview]
Message-ID: <20080309115427.2f39dc93.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10205-10286@http.bugzilla.kernel.org/>
On Sun, 9 Mar 2008 08:55:52 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10205
>
> Summary: BUG: Display gets corrupted when using lxfb driver on a
> GeodeLX 5535 based chipset
> Product: Drivers
> Version: 2.5
> KernelVersion: 2.6.24.2
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Console/Framebuffers
> AssignedTo: jsimmons@infradead.org
> ReportedBy: nestorac@gmail.com
>
>
> Latest working kernel version:
> None or unknown
> Earliest failing kernel version:
> Latest version
> Distribution:
> Debian Stable (Etch)
> Hardware Environment:
> AMD Geode 32 bit A830 board, 5536 chipset based embedded computer (TFT 10"
> 800x600), with GeodeLX embedded GPU. It's webpage is at:
> http://www.winmatev.com.tw/PPc/PPcSpec.asp?Prod=03_0013&Typeid=03020101
> I own a cheaper version using GeodeGX 500 processor, 256MiB RAM, no
> touchscreen.
> Software Environment:
> Debian 4.0 Stable (Etch), Kernel 2.4.22.2 vanilla + AUFS patch (it has nothing
> to do with graphics, but BTW...), all i386, kernel specifically compiled for
> Geode GX/LX Processor target (but also does not work for generic i386 target).
> Problem Description:
> I get a blurry screen when trying to enable Framebuffer, vga=788
> option (800x600). Screen gets corrupted, but when I start X.org, it shows
> Ok, until I switch again to console. Everything works fine with Vesa FB,
> except that, of course, it's more CPU consuming and slower [supposedly].
> When blurry, screen looks like it was under a lake.
> Steps to reproduce:
> 1) Compile the kernel, include support for GeodeLX Framebuffer.
> 2) Install the kernel on the machine
> 3) Boot it up, adding vga=788 mode to bootloader.
> 4) Screen gets completely blurry until X.org starts.
>
Guys, this is a post-2.6.24 regression hence needs
running-around-with-your-hair-on-fire priority please.
Can anyone think what we did to cause this? Recent changes to
drivers/video/geode/ look pretty tame.
-------------------------------------------------------------------------
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/
next parent reply other threads:[~2008-03-09 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10205-10286@http.bugzilla.kernel.org/>
2008-03-09 18:54 ` Andrew Morton [this message]
2008-03-09 21:31 ` [Bugme-new] [Bug 10205] New: BUG: Display gets corrupted when using lxfb driver on a GeodeLX 5535 based chipset Rafael J. Wysocki
2008-03-09 22:54 ` Andrew Morton
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=20080309115427.2f39dc93.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jordan.crouse@amd.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=nestorac@gmail.com \
--cc=rjw@sisk.pl \
/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).