gt; struct reservation_object __builtin_resv;
> };
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index 5098228f1302..4f8b368ac4e2 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/inte
{
> + if (fence->ops != &drm_crtc_fence_ops)
> + return NULL;
> +
> + return container_of(fence->lock, struct drm_crtc, fence_lock);
> +}
> +
> /**
> * struct drm_connector_state - mutable connector state
> * @connector: backpointer to the connector
> --
> 2.5.5
>
> ___
> dri-devel mailing list
> dri-de...@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel OTC
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
E_OBJECT_CRTC);
> if (!prop)
> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> index 8cb377c..5ba3cda 100644
> --- a/include/drm/drm_crtc.h
> +++ b/include/drm/drm_crtc.h
> @@ -2122,6 +2122,7 @@ struct drm_mode_config {
> struct drm_property *prop_crt
ebase to use only stacked sync_file_info
>
> Why are these vX things here in the changelog?
That's how we usually roll in gpu land.
--
Ville Syrjälä
Intel OTC
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
On Mon, Nov 16, 2015 at 12:02:51PM -0500, ira.weiny wrote:
> On Mon, Nov 16, 2015 at 07:29:46PM +0300, Dan Carpenter wrote:
> > Ville Syrjälä already posted the answer but his email had no text just a
> > link inside 300+ lines of quoted output so you may have missed it.
>
&
> c0 40 42 0f 00 48 f7 f6 f6 43 74 10 41 89 c4 75 26 f6 05 fa 6f 03 00 01 <45>
> 89
> 96 b0 00 00 00 45 89 a6 ac 00 00 00 75 35 48 83 c4 08 5b
> [ 11.232990] RIP []
> drm_calc_timestamping_constants+0x86/0x130 [drm]
> [ 11.232991] RSP
> [ 11.232992] CR2: 0
I agree this information should not be coming from
> userspace). Seems like the sort of thing that the bridge or encoder
> could set on the adjusted_mode.
Probably better to not mix user visible and internal flags in
drm_display_mode.flags. Just
On Wed, Oct 23, 2013 at 04:48:51PM +0200, Denis Carikli wrote:
> Hi,
>
> On 10/18/2013 09:46 AM, Ville Syrjälä wrote:
> >> +#define DRM_MODE_FLAG_PDATEN (1<<22)
> >> +#define DRM_MODE_FLAG_NDATEN (1<<23)
> >&g
(1<<24)
> +#define DRM_MODE_FLAG_NPIXDATEDGE(1<<25)
Do we really need to make this stuff visible to userspace?
And there's no documentation to explain any of it.
>
> /* DPMS flags */
> /* bit compatible with the xorg definitions. */
> --
> 1.
