svn commit: r433902 - head

[Alexey Dokuchaev]

On Thu, Apr 20, 2017 at 07:53:50PM +0200, Matthew Rezny wrote:
> On Thursday 20 April 2017 17:08:37 Alexey Dokuchaev wrote:
> > ...
> > Can you recall what was the previous order?
> 
> Old Order: vendor specific according to PCI ID, fbdev, vesa
> ...
> Modesetting was behind an #ifdef linux. I enabled it for us as well, though
> it could probably be changed to be enabled for all BSDs upstream.
> 
> See x11-servers/xorg-server/files/patch-hw_xfree86_common_xf86AutoConfig.c

Thanks for the pointer, I'll have a look.  Meanwhile I've noticed another
problem: hw accel no longer works ("unknown chip id 0x990d, can't guess.")
but that's better to be reported on the x11@ list.

> > Any ideas why it does not work now with AMD A8 APU (Aruba, NI)?  I don't
> > mind loading it by hand or via kld_list, but still want to know what had
> > broken automatic loading in my case (as it worked fine before).
> 
> Do you have xf86-video-ati installed? That is what loads radeonkms.ko.
> You should only need to manually load it if using modesetting (ati is not
> installed).

Yes, I do have (and always had) xf86-video-ati installed.

> > Can you elaborate a bit on the last sentense (my context is solely AMD/ATI,
> > I don't own or care about Intel hardware).  Thanks,
> 
> The modesetting driver is meant to be a generic DDX that uses the ksm drm
> interface without any vendor specifics. Think of it like scfb sitting on
> the framebuffer, except it sits on drm so it can do OpenGL and actually uses
> that exclusively for accelerated rendering (Glamor for 2D). That is nice to
> have in general and could be a good improvement for some Intel GPUs since
> UXA and SNA aren't exactly stable and Intel hasn't done a release in years.
> [...]

Appreciate elaborate reply; I'd have to return to it later after I educate
myself on the subject better. :-)

./danfe