On Thu, 2012-02-23 at 12:15 -0800, Linus Torvalds wrote: > Btw, clearly X does *not* cache the EDID results, at least not for > this case. So the explicit xrandr example is probably pretty close to > what wine does. Maybe the proper fix is to just make X.org force > caching when clients do this (because it's definitely X that does the > drm_mode_getconnector() thing - xrandr itself spends zero time on > this, it just does an X request and waits for the result). RANDR exposes two requests here for a reason. We used to only have RRGetScreenResources which always pulled data afresh. We added RRGetScreenResourcesCurrent to get the cached version. If you want xrandr(1) to use the latter say xrandr --current. Arguably xrandr should do things the other way around and require you to say --reprobe or something. Even then, the kernel should cache if it can. And any competent hardware has plug interrupts on DP and DVI, so we really should get this right. - ajax
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel