On Monday, December 14, 2015 7:11 PM, Мартин Бохниг <[email protected]>
wrote:
Hi Ken,
did you ever have a look at the hw support matrix of the last ums (aka non-kms)
Intel 2.6.3->2.9.1 ddx???
It is suited for museum presentations, showing that DRM/DRI was already
available in the steam/coal age.
For radeon: Sure, but that wasn't even scratched so far.
(and it is complicated/impossible to maintain the same drm submodule for
different revisions of radeon-drm and intel-drm [must be based on the same
revision]).
But as OI uses the final ums-radeon ddx and currently has no working modern kms
based intel-drm, our only solution is to stick with the old stuff you just
mentioned for the time being, unfortunately ...
For new GPU's - for now - the only solution continues to be the vesa ddx plus
the console-resolution change utility.
%martin
------------------->
Martin,
Yes. I reviewed the HW matrix and also wrote a wiki on Intel GPU tools I
compiled/ported for OI as it evolves.
The bigger question is if the needed 'kernel source code to fully support
XServer 1.17.x driver infrastructure' as implemented in Oracle Solaris is made
publically available - as it relates to fully supporting 'any'
Intel/Radeon/AMDGPU driver hardware accelerated capabilities and features.
I may have mistaken Randy's XDC 2015 presentation on drm/kms (i915) upstream
driver support on this effort.See: http://lanyrd.com/2015/xdc2015/sdthhq/
Earlier this year we were going to push out XServer 1.17.x for oi-hipster and
relax support for the Intel/Radeon drivers.The Nvidia driver works fine for any
true 2D/3D graphics work. Intel/Radeon open source driver support is still
'spotty'on Linux.
Maybe, to move forward and not backward, we could do just that. Push out
Xserver 1.17.4 and review alternative or unified methods to support
Intel/Radeon drivers from that point.
Just a thought...
Ken
_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev
