On Thu, May 7, 2009 at 11:20 AM, Martin Bochnig <martin at martux.org> wrote: > On Thu, May 7, 2009 at 7:32 AM, Gordon Johnson <gcjohns at hotmail.com> wrote: >> I need the r6xx-r7xx-drm support too. >> >> Here are the instructions from xorg's radeonhd branch to make drm support 2D >> acceleration in r6xx - r7xx: >> >> ___________________________________________________________________ >> cd drm/linux-core >> ? git checkout -b r6xx-r7xx-support origin/r6xx-r7xx-support >> ? make radeon.o drm.o >> ? find /lib/modules -name "radeon.ko" -o -name "drm.ko" >> ? sudo cp radeon.ko /lib/modules/YOUR_KERNEL_VERSION/.../radeon.ko >> ? sudo cp drm.ko /lib/modules/YOUR_KERNEL_VERSION/.../drm.ko >> ___________________________________________________________________ >> >> Please forgive my ignorance. ?I am no linux expert, but my understanding is >> that filetype '.ko' is a linux kernel modification file with localization >> options applied. >> >> I haven't a clue how to implement these instructions on OpenSolaris. >> >> If I understand previous posters, then I have to wait for Solaris to move >> some drm functionality into the kernel as BSD and Linux have. And I >> understand that won't be done until sometime after 2009-06. >> >> Did I understand that right? >> >> Or does someone have a Solaris version of the above r6xx-r7xx support >> instructions?
Errm, to answer your actual question, forget about easy 5 minutes instructions. The only easy thing that might work could potentially be, that you would patch/customize the radeon DRM driver that is part of OS/Net, and that you work with bldenv, until you have something that works for you. However, if the DRM version in OS/Net is still the same hopelessly outdated one, then I doubt that you can make the brand-newest chipsets function simply by adding a few pciids or patching a few header files. Anyway, working with bldenv inside OS/Net would be your _only_ starting point, forget building the default standalone DRM gate as you check it out from freedesktop.org . You must start with the Solaris-ported (obsolete) version in OS/Net and maybe you are lucky enough that you can update a few things without breaking stuff (the build, but also behavior at link- and run- time). Much luck! >> >> THANKS! >> >> Gordo > > > Hello, the Solaris radeon DRM port never made it upstream into the DRM > repo, instead it went into OS/Net. > > Half a year ago I carefully isolated the changes (first found out > matching file versions in DRM git, from file to file not always the > same git id / date, then created diffs, file for file, then carefully > removed unnecessary stuff such as cosmetic changes, port to SunStudio > and so forth). I have those modified diffs on hdd. Then my goal was to > take a more recent git and merge the DDI/DDK relevant modifications > in. This did not easily function due to significant architectural > changes inside DRM vs. LinUX kernel 2.6.x interaction (more io now > done directly by kernel, rather than userland libs). > The best I could do reasonably easy (for an unpaid ?hobby project), > would be, that I could bring the radeon DRM version that is part of > OS/Net 10 months into the future (still only summer 2007). This is not > what you want. The main reason why I completely stopped it is, that I > was told, that Sun China is already working on updating Ati-DRM to a > really recent version. This means a whole team of highly skilled > experienced engineers is working on that during their paid time. So > ask Alan Coopersmith for details. > > With above method it is also doable, to add DRI/DRM support to some of > the other chipsets, which are not yet supported by Solaris. At least > to level summer 2006 I could do this. But for one person alone it is > still a bit oversized. Is anybody interested? > > > %martin >
