On 11 November 2015 at 16:48, Brian Paul <bri...@vmware.com> wrote: > On 11/11/2015 08:44 AM, Emil Velikov wrote:
>> >> I have seen similar type of documents in the past, most of which going >> out of date very quickly due to distribution changes and/or others. >> Wondering how you'll feel about "check your distro and add svga to the >> gallium-drivers array" style of instructions ? > > > I'm afraid I don't quite understand what you're saying there. Can you > elaborate? > > Rather than walking through the requirements, configure and make/make install steps, just forward people to the distro specific wiki on "how to build mesa/kernel" and explicitly mention the differences: mesa: - XA must be enabled: --enable-xa - svga must be listed in the gallium drivers: --with-gallium-drivers=svga... kernel: - Set DRM_VMWGFX others... Related: does the upstream [1] vmwgfx module work well when combined with upstream core drm across different versions ? Considering how well Thomas is handling upstreaming shouldn't the module from the kernel be recommended ? For example some of us had nasty experiences where versions of vmware player/workstation ships/builds/uses kernel modules which "clash" with the ones already bundled in the kernel package. With "clash" - there is no guarantee whether the upstream or downstream module gets loaded, and due difference in the symbols provided one does encounter "function_foo() error Invalid argument" type of messages, and ultimately things just not working. Thanks Emil [1] http://cgit.freedesktop.org/mesa/vmwgfx/ _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
