On Fri, 10 Oct 2003 [EMAIL PROTECTED] wrote: >What is the status of the problem of being unable to restore the >VGA screen using the SiliconMotion drivers?
The status of the problem is whatever the bug report states. If it doesn't state what you'd like to hear, then that is because nobody has anything to comment as of yet about the report(s), and nobody is likely investigating the problem. >Bugzilla 124 & 702 have reported the problem. Some comments >indicate there is a working patch, while some comments (and my >experience) indicate that the problem still exits, even using >the latest 4.3.99.x XFree86. It's not clear if anyone is >actively working on the problem. The bug is reported against XFree86 4.3.0 on ia32. I doubt there are many people who: 1) Even have silicon motion hardware 2) Have the hardware you are having problems with 3) Are running NetBSD 4) Can reproduce your problem 5) Have had the time and interest in investigating the issue. >I would add that in my case, using a Panasonic CF-28 ToughBook >(laptop), the problem exists using Solaris 8 and 4.3.99.x >XFree86, but does NOT exist using RedHat Linux with 4.2 XFree86 >on the same machine. Also, as I reported in Bugzilla 702, using >Solaris 8 and 4.0.2 XFree86 Porting Kit, I did not have the >problem either. If 4.2.x works for you, why don't you just continue using 4.2.x? Or alternatively, extract a binary 4.2.x driver module from the older release and rename the 4.3.0 driver and plop the old one that worked in its place. >I would appreciate feedback on any planned efforts on this >problem. If any XFree86 Developer in the LA area needs to look >at my machine, I may be able to accommodate them to get this >problem solved. Everyone working on XFree86 does so as a volunteer. When people report bugs, if there is a volunteer who works in that area of code, be it a library, the X server, or a driver module, etc. and they have the time and inclination, and the problem interests them to fix, they generally respond to reports and fix them. If you display all bug reports, you'll notice the majority of them are fixed and closed. Since this issue is open still, that possibly means nobody is interested in hacking on an ancient video driver for ancient video hardware, so the bug stays open until someone comes along and volunteers to fix it, and submits a patch. That could well be an existing XFree86 developer, or someone such as yourself. More likely than not however, whoever fixes it (if it ever does get fixed) will be someone who actually has the hardware themselves. There really aren't enough volunteer developers out there to endlessly maintain every single video driver and keep it working on every piece of video hardware, and respond to problem reports instantly and fix all issues and fix them quickly. If you're unable to fix the problem yourself and submit a patch onto that bug report, you might find my previous suggestion of using the 4.2.1 video driver in 4.3.0 to be a useable workaround for now. Hope this helps. -- Mike A. Harris _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
