Displaying 3 results from an estimated 3 matches for "driver_virtual".
2023 May 04
0
[PATCH v2 1/8] drm: Disable the cursor plane on atomic contexts with virtualized drivers
...@@ enum drm_driver_feature {
> > > > > > ????? * synchronization of command submission.
> > > > > > ????? */
> > > > > > ???? DRIVER_SYNCOBJ_TIMELINE???????? = BIT(6),
> > > > > > +??? /**
> > > > > > +???? * @DRIVER_VIRTUAL:
> > > > > > +???? *
> > > > > > +???? * Driver is running on top of virtual hardware. The most significant
> > > > > > +???? * implication of this is a requirement of special handling of the
> > > > > > +???? * cursor plane (e...
2023 May 04
0
[PATCH v2 1/8] drm: Disable the cursor plane on atomic contexts with virtualized drivers
...> > > for "universal planes" to expose atomic kms paths.
> > >
> >
> > After some discussion on the #dri-devel, your approach makes sense and the
> > only contention point is the name of the driver feature flag name. The one
> > you are using (DRIVER_VIRTUAL) seems to be too broad and generic (the fact
> > that vkms won't set and is a virtual driver as well, is a good example).
> >
> > Maybe something like DRIVER_CURSOR_HOTSPOT or DRIVER_CURSOR_COMMANDEERING
> > would be more accurate and self explanatory ?
>
> Sur...
2023 May 04
0
[PATCH v2 1/8] drm: Disable the cursor plane on atomic contexts with virtualized drivers
...xpose atomic kms paths.
> > > > >
> > > >
> > > > After some discussion on the #dri-devel, your approach makes sense and the
> > > > only contention point is the name of the driver feature flag name. The one
> > > > you are using (DRIVER_VIRTUAL) seems to be too broad and generic (the fact
> > > > that vkms won't set and is a virtual driver as well, is a good example).
> > > >
> > > > Maybe something like DRIVER_CURSOR_HOTSPOT or DRIVER_CURSOR_COMMANDEERING
> > > > would be more accurate...