Lines Matching full:there

34 implementation (there's lots of outdated locking leftovers in various
49 There is a conversion guide for atomic and all you need is a GPU for a
78 Aside from the clipped coordinates right above there's a few suboptimal things
102 now, but there's still a pile of existing drivers that easily could be
118 a bit too severe. So there's some follow-up work to adjust the function
132   implement the userspace ABI. And then there's the optional hooks for the
135   ``_helper_funcs`` since they are not part of the core ABI. There's a
152 and there's a ``gem_free_object_unlocked`` callback for any drivers which are
189 drm_mode_config_helper_suspend/resume(). Also there's still open-coded version
238 There's drm_gem_prime_mmap() for this now, but still needs to be rolled out.
280 SCROLL_REDRAW. There's a ton of code this will allow us to remove:
460 execute locklessly so there are serious concerns with dereferencing
486 * There's a massive confusion of different panic handlers. DRM fbdev emulation
492   returns true if there's a panic going on for real, and fix up all the
507 * There's also proposal for a simplied DRM console instead of the full-blown
518 There's a bunch of issues with it:
524   maybe other kms objects directly in core. There's even drm_print support in
525   the funcs for these objects to dump kms state, so it's all there. And then the
551 - Make ->funcs and ->helper_private vtables optional. There's a bunch of empty
558   end, for which we could add drm_*_cleanup_kfree(). And then there's the (for
641 AMD DC is the display driver for AMD devices starting with Vega. There has been
642 a bunch of progress cleaning it up but there's still plenty of work to be done.
651 There is support in place now for writing internal DRM clients making it
671 There are plenty of fbdev drivers for older hardware. Some hwardware has