| Summary: | neomagic regression in 6.8.1: very slow scrolling with xterm under X11 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Igor Bukanov <ml> | ||||||||||
| Component: | Driver/Neomagic | Assignee: | Egbert Eich <eich> | ||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||
| Severity: | normal | ||||||||||||
| Priority: | high | CC: | eich, keithp, roland.mainz, shrek | ||||||||||
| Version: | 6.8.1 | ||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Igor Bukanov
2004-11-22 00:05:56 UTC
I can confirm this on a Dell Latitude Cpi Neomagic installation. It is not only the xterm scrolling, but all text scrolling applications. For example my exmh is very badly affected. reproduce on IBM TP570 Created attachment 1362 [details] [review] undo 6.7.0 this patch seems a little drastic. the changes to neo_video.c for instance shouldn't have any affect on your chip. If possible, could you track down what exact change causes the problem? it shouldn't be too hard since the changes are pretty minimal. The patch is definitely not the solution. I'm the maintainer of this driver and I'm going to look at this as soon as I'm organized again. Created attachment 1414 [details] [review] xorg-x11-6.8.0-alt-neomagic this problem is fixed by this patch Your patch backs out the XAA wrapper that is necessary for the pseudocolor emulation. I've discovered some problems with the wrapper today which I will address ASAP. Created attachment 1480 [details] [review] Fix This patch should fix the issues with the neomaic driver. It also contains two fixes that are yet missing from the tree. A large part of this fix backs out some #if 0'ed stuff. Created attachment 1481 [details] [review] [FIXED_X11R68x] Fix (update) This overrides the previous patch which was created from a slightly wrong version. This has been committed to head. Please reopen when you still see problems. Is it possible to get a compiled driver for testing? Keith, can you review this patch please, in particular the composite change, for the sake of the maintenance release? Keith: ping! The change to fbwindow.c shouldn't be necessary; we always build with COMPOSITE support. That said, I think the COMPOSITE code in that case is probably correct even without COMPOSITE defined. As for the rest of the changes, I don't have any idea what xaaWrapper is for. Comment on attachment 1481 [details] [review] [FIXED_X11R68x] Fix (update) Approval for X11R6.8.x stable branch granted in the 2004-12-13 release-wranglers phone call. Comment on attachment 1481 [details] [review] [FIXED_X11R68x] Fix (update) Patch checked-in into X11R6.8.x stable branch: /cvs/xorg/xc/ChangeLog,v <-- ChangeLog new revision: 1.365.2.102; previous revision: 1.365.2.101 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. /cvs/xorg/xc/programs/Xserver/fb/fbwindow.c,v <-- fbwindow.c new revision: 1.4.2.1; previous revision: 1.4 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. /cvs/xorg/xc/programs/Xserver/hw/xfree86/xaa/xaaWrapper.c,v <-- xaaWrapper.c new revision: 1.1.2.1; previous revision: 1.1 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. /cvs/xorg/xc/programs/Xserver/mi/micmap.c,v <-- micmap.c new revision: 1.3.4.1; previous revision: 1.3 cvs commit: Using deprecated info format strings. Convert your scripts to use the new argument format and remove '1's from your info file format strings. Mailing the commit message to xorg-commit@lists.freedesktop.org... |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.