<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yiv2974719208"><div id="yui_3_16_0_1_1450196768364_8756"><div id="yui_3_16_0_1_1450196768364_8755" style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><br clear="none"><br><div class="qtdSeparateBR"><br><br></div><div class="yiv2974719208yqt8723421261" id="yiv2974719208yqt61411"><div id="yui_3_16_0_1_1450196768364_8968" class="yiv2974719208yahoo_quoted" style="display:block;"> <div id="yui_3_16_0_1_1450196768364_8967" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div id="yui_3_16_0_1_1450196768364_8966" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr"><font face="Arial" size="2"> On Monday, December 14, 2015 7:11 PM, Мартин Бохниг <opensxce@mail.ru> wrote:<br clear="none"></font></div> <br clear="none"><br clear="none"> <div id="yui_3_16_0_1_1450196768364_8965" class="yiv2974719208y_msg_container"><div id="yiv2974719208"><div id="yui_3_16_0_1_1450196768364_8964">Hi Ken,<br clear="none"><br clear="none">did you ever have a look at the hw support matrix of the last ums (aka non-kms) <em id="yui_3_16_0_1_1450196768364_8963">Intel 2.6.3->2.9.1 ddx???<br clear="none">It is suited for museum presentations, showing that DRM/DRI was already available in the steam/coal age.<br clear="none"><br clear="none"><br clear="none">For radeon: Sure, but that wasn't even scratched so far.<br clear="none">(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]).<br clear="none">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 ...<br clear="none"><br clear="none"><br clear="none">For new GPU's - for now - the only solution continues to be the vesa ddx plus the console-resolution change utility.<br clear="none"><br clear="none"><br clear="none">%martin</em><div class="yiv2974719208yqt4843548440" id="yiv2974719208yqtfd36165"><em id="yui_3_16_0_1_1450196768364_8980"><br clear="none"><br clear="none"></em><div id="yui_3_16_0_1_1450196768364_9126"><em id="yui_3_16_0_1_1450196768364_8980">-------------------></em></div><div id="yui_3_16_0_1_1450196768364_9165"><br><em id="yui_3_16_0_1_1450196768364_8980"></em></div><div class="" id="yiv2974719208yui_3_16_0_1_1450196768364_4428">Martin,</div><div class="" id="yiv2974719208yui_3_16_0_1_1450196768364_4426"><br class="" id="yui_3_16_0_1_1450196768364_9131" clear="none"></div><div class="" id="yiv2974719208yui_3_16_0_1_1450196768364_4424">Yes. I reviewed the HW matrix and also wrote a wiki on Intel GPU tools I compiled/ported for OI as it evolves.<br class="" id="yui_3_16_0_1_1450196768364_9134" clear="none"></div><div class="" id="yiv2974719208yui_3_16_0_1_1450196768364_5883"><br class="" id="yui_3_16_0_1_1450196768364_9137" clear="none"></div><div class="" id="yiv2974719208yui_3_16_0_1_1450196768364_5884">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.</div><div class="" id="yiv2974719208yui_3_16_0_1_1450196768364_6554"><br class="" id="yui_3_16_0_1_1450196768364_9141" clear="none"></div><div id="yui_3_16_0_1_1450196768364_9142">I may have mistaken Randy's XDC 2015 presentation on drm/kms (i915) upstream driver support on this effort.<em id="yui_3_16_0_1_1450196768364_8980"></em></div><div dir="ltr"><em id="yui_3_16_0_1_1450196768364_8980"></em></div></div><em></em><div class="yiv2974719208yqt4843548440" id="yiv2974719208yqtfd93794"><div dir="ltr" id="yui_3_16_0_1_1450196768364_9144">See: <a id="yui_3_16_0_1_1450196768364_9720" href="http://lanyrd.com/2015/xdc2015/sdthhq/">http://lanyrd.com/2015/xdc2015/sdthhq/</a></div><div id="yui_3_16_0_1_1450196768364_9739" dir="ltr"><br></div><div id="yui_3_16_0_1_1450196768364_9144">Earlier this year we were going to push out XServer 1.17.x for oi-hipster and relax support for the Intel/Radeon drivers.</div><div id="yui_3_16_0_1_1450196768364_12691">The Nvidia driver works fine for any true 2D/3D graphics work. Intel/Radeon open source driver support is still 'spotty'</div><div>on Linux. <br></div><div id="yui_3_16_0_1_1450196768364_10411"><br></div><div id="yui_3_16_0_1_1450196768364_11774" dir="ltr">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.</div><div id="yui_3_16_0_1_1450196768364_12105" dir="ltr"><br></div><div id="yui_3_16_0_1_1450196768364_13624" dir="ltr">Just a thought...<br></div><div id="yui_3_16_0_1_1450196768364_12098" dir="ltr"><br></div><div id="yui_3_16_0_1_1450196768364_12100" dir="ltr">Ken</div><div id="yui_3_16_0_1_1450196768364_12102" dir="ltr"><br></div><div id="yui_3_16_0_1_1450196768364_13626" dir="ltr"> <br></div><div id="yui_3_16_0_1_1450196768364_9146"><br clear="none"></div></div></div></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></div></div></div></body></html>