2009/7/11 Uros Nedic <urosn at live.com>: > Thank you for reply Edward. > I'm already reading your post on auroraux :), and > startet to talk on freenode.net with radeon guys > to see what part of software we have to port particulary. > > It looks like that we have to change to or three files > or rewrite. All other stuffs belong to DRI-core and it is not > part of our job :) DRI community does that. After we finish our > job we just need to recompile and integreade DRI for each > new release.
It is not as trivial. The "other" files are heavily outdated. You cannot "slightly update or rewrite a bit" those 3 device specific files in complete isolation. Either you upgrade all, or nothing. But as you are the mentor, I thought you tell us how to overcome the problems I outlined circa 6 months ago on driver-discuss: #################### http://opensolaris.org/jive/thread.jspa?messageID=375640 //##### Well, the problem with upgrading DRM: I bet it has to do with moving some functionality into (Linux- and BSD-) kernel on 2007-07-21 01:16:42 (GMT) , which is not yet in the Solaris kernel. More precisely with this global patch (affecting all vendors, not only ati) : """Replace DRM_IOCTL_ARGS with (dev, data, file_priv) and remove DRM_DEVICE. The data is now in kernel space, copied in/out as appropriate according to the This results in DRM_COPY_{TO,FROM}_USER going away, and error paths to deal with those failures. This also means that XFree86 4.2.0 support for i810 DRM is lost. """ http://cgit.freedesktop.org/mesa/drm/commit/?id=5b38e134163cc375e91424c4688cc9328c6e9082 . This prevents the entire DRM-Upgrade porting approach from being a dumb merge of Sun's existing port into the current git. Also: Isolating the actually important changes has not been fun, as 80% of the changes were bloating like sometimes changing // comments into /* ... */ ones, and other times the other way around (makes sense!!). Also things like eliminating tabs in header file #define chains, while systematically putting new \t ' s into other places of the code. I had to go through thousands and thousands of lines of the diffs to delete all the cosmetic stuff, allowing me to see what's really required to make things work for the DDi/DKI interface. My goal is, that the code can go upstream into http://cgit.freedesktop.org/mesa/drm . And it is halfway trivial to achieve this. Only an abundance of work is required. That's my current project. Then it will be easier and cheaper (!) for Sun to keep the DRM code in sync with developments. Thoughts? ##### // #################### Before asking holes in Minskey's stomach I suggest, you first study the code. ALL code, from all periods since 2006 (in DRI's git and OS/Net's hg). Then we talk again. That's the only way. Okay. Edward: All the best to you, too. In my case it did not help, but that's another story. Yes, your AuroraUX ml: I sure join it soon, must join MilaX and BeleniX as well. Congrats to your Distro-project. Regards for now, Martin
