Adding 662 path to the driver
Created attachment 8217 [details] [review] patch for 662 path adding path for 662
Created attachment 8218 [details] [review] add 662 path add 662 path
add 662 path
Created attachment 8219 [details] add 662 path add 662 path
can you please attach a diff relative to the current driver? trying to just pick the changes out is difficult.
This "patch" (ie the code) is totally flawed and full of bugs. Don't even think about using it.
Dear Thomas: Nice to hear you from the bugzilla. The driver I attached is based on what you mail to me on 2005/12/20 and it is quite like the one which included in xorg6.9.0. Below I list what I remembered that I added in. 1. adding pcie interface enabling sequence. 2. TV timing. 3. fix 662 single CRT garbage. I also list some already known bugs that I have no time to fix. 1. the channel A does not work properly. 2. The s-video TV has some wrong timeing in channel B After 2005/12, I lost you and have no idea how to contact you. I have build that driver within xorg7.1 and run it on both 662 single CRT and 662/761gx+307LV/cp in channl B with DVI or LVDS. After comparing the driver on git repository with this one, I found you modify the driver initialization sequence, change some 550 path and reorder the chipId enum sequence,etc. I have mailed the driver to the mail box, thomas@winischhofer.net, and want to get your consent before putting it on the bugzilla. My job has transfered to XP-video/DirectDraw driver and some customers want to get some ok driver to run 662 single CRT from Xorg, so I brutally put the whole driver source rather than diff on bugzilla. If you have any question please let me know. appreciate your help and sincerely hope you fine, cckuo
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
*** Bug 12813 has been marked as a duplicate of this bug. ***
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
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.