From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: jochen@jochen.org
Subject: Fw: [Bugme-new] [Bug 4386] New: tridentfb with ACCEL leaves artefacts when scrolling
Date: Tue, 22 Mar 2005 12:45:01 -0800 [thread overview]
Message-ID: <20050322124501.6c4573a1.akpm@osdl.org> (raw)
Jochen, it would be useful if you could test 2.6.12-rc1-mm1.
Also, did this driver work OK in earlier kernels? If so, which versions?
Begin forwarded message:
Date: Tue, 22 Mar 2005 08:15:18 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4386] New: tridentfb with ACCEL leaves artefacts when scrolling
http://bugme.osdl.org/show_bug.cgi?id=4386
Summary: tridentfb with ACCEL leaves artefacts when scrolling
Kernel Version: 2.6.11.5
Status: NEW
Severity: normal
Owner: jsimmons@infradead.org
Submitter: jochen@jochen.org
Distribution: Debian/sarge
Hardware Environment: Mini-ITX with trident on board, C3 CPU
Problem Description:
When compiling tridentfb with
CONFIG_FB_TRIDENT=y
CONFIG_FB_TRIDENT_ACCEL=y
booting leaves the end of long lines in the last line on screen when scrolling.
When X is running, scrolling puts garbage on the screen (looks like X data)
Console switch fixes the screen.
Behaviour seems to be identical with noaccel and without on the video=tridentfb
parameter in lilo.conf.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
reply other threads:[~2005-03-22 20:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050322124501.6c4573a1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jochen@jochen.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).