Comment 162 for bug 301958

Hello, I have been out on another non-profit, making a conference on advanced audio and electroacoustics, there I am a pro, not in video...@tpurch, it seems as I told Martin in private I used some branch of your published code on the last version with a few modifications i did. The code used before was another branch, which was not 1366x768 compatible. If it has debug sumbols that will be on the makefile, and quite frankly, the driver looks quite the same in terms of size...who knows, i'm (very) familiar with dsp fixed-point assembler, kernel drivers I didn't touched those since win32, did about 4, written in 32-bit 8086 assembler.

Coming back to the latest code, I have a few notes taken, told Martin that I would ship the source to him and yes. He will have the code and instructions this week, I will publish those, after I finally sit down and look at what I did to make that totally patched code compatible with Maverick.

No tracking records exist for that code, and everything is a mess, that's why this has to gain access to tracked repositories. I tried to diff those from previous versions anad was a little astonished, and evn produced a code migrating directly from 8.10 to Maverick, but the flaws were there.

From the results patent on-screen when starting up, there are problems to be solved in this driver. When I picked up from the changes made after 9.04, the driver was already an unfriendly one (Plymouth incompatibility), so my 9.04 version, which source code I preserve, should be the basis for any changes, but taking into account all the others since 8.10. Fortunately I kept just about everything.

Now it is time to organize it and deliver it to who will be in charge. What I did up to the moment was trying to avoid the worst, keeping good people using a nice, community-maintained system. But, again, community-maintained does not mean chaos, and so it is good that things will be getting back on track, because there are huge quantities of these systems around the world.

If this does not enter the current branch in xorg, I will continue to patch, because I still have a couple of this systems around. What I cannot do is to retrace the past work. I don't have the immediate expertise or time to do that.

All the best

Antonio