Just some cleanups for unused fields in drm_crtc.h and some comment
corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
actually weren't as bad as I feared).
Next step is to remove a whole slew of DRM_DEBUG calls unless people are
really attached to them. I find them to just get
Just some cleanups for unused fields in drm_crtc.h and some comment
corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
actually weren't as bad as I feared).
Next step is to remove a whole slew of DRM_DEBUG calls unless people are
really attached to them. I find them to just get
Just some cleanups for unused fields in drm_crtc.h and some comment
corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
actually weren't as bad as I feared).
Next step is to remove a whole slew of DRM_DEBUG calls unless people are
really attached to them. I find them to just get
Just some cleanups for unused fields in drm_crtc.h and some comment
corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
actually weren't as bad as I feared).
Next step is to remove a whole slew of DRM_DEBUG calls unless people are
really attached to them. I find them to just get
Just some cleanups for unused fields in drm_crtc.h and some comment
corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
actually weren't as bad as I feared).
Next step is to remove a whole slew of DRM_DEBUG calls unless people are
really attached to them. I find them to just get
Just some cleanups for unused fields in drm_crtc.h and some comment
corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
actually weren't as bad as I feared).
Next step is to remove a whole slew of DRM_DEBUG calls unless people are
really attached to them. I find them to just get
On Mon, Nov 7, 2011 at 3:03 PM, Jesse Barnes wrote:
> Just some cleanups for unused fields in drm_crtc.h and some comment
> corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
> actually weren't as bad as I feared).
>
> Next step is to remove a whole slew of DRM_DEBUG calls unles
On Mon, Nov 7, 2011 at 3:03 PM, Jesse Barnes wrote:
> Just some cleanups for unused fields in drm_crtc.h and some comment
> corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
> actually weren't as bad as I feared).
>
> Next step is to remove a whole slew of DRM_DEBUG calls unles
On Mon, Nov 7, 2011 at 3:03 PM, Jesse Barnes wrote:
> Just some cleanups for unused fields in drm_crtc.h and some comment
> corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
> actually weren't as bad as I feared).
>
> Next step is to remove a whole slew of DRM_DEBUG calls unles
On Mon, Nov 7, 2011 at 3:03 PM, Jesse Barnes wrote:
> Just some cleanups for unused fields in drm_crtc.h and some comment
> corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
> actually weren't as bad as I feared).
>
> Next step is to remove a whole slew of DRM_DEBUG calls unles
On Mon, Nov 7, 2011 at 3:03 PM, Jesse Barnes wrote:
> Just some cleanups for unused fields in drm_crtc.h and some comment
> corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
> actually weren't as bad as I feared).
>
> Next step is to remove a whole slew of DRM_DEBUG calls unles
On Mon, Nov 7, 2011 at 3:03 PM, Jesse Barnes wrote:
> Just some cleanups for unused fields in drm_crtc.h and some comment
> corrections. I also removed a few DRM_ERRORs from drm_crtc.c (things
> actually weren't as bad as I feared).
>
> Next step is to remove a whole slew of DRM_DEBUG calls unles
This is the complete set of patches that yield a working 3-pipe mode
setting configuration on my test machines. It does not make DPMS work,
so I still need to figure that out. As the DPMS paths are almost
entirely different from mode setting (whose crazy idea was that,
anyway?), that may take a bit
This is the complete set of patches that yield a working 3-pipe mode
setting configuration on my test machines. It does not make DPMS work,
so I still need to figure that out. As the DPMS paths are almost
entirely different from mode setting (whose crazy idea was that,
anyway?), that may take a bit
This is the complete set of patches that yield a working 3-pipe mode
setting configuration on my test machines. It does not make DPMS work,
so I still need to figure that out. As the DPMS paths are almost
entirely different from mode setting (whose crazy idea was that,
anyway?), that may take a bit
This is the complete set of patches that yield a working 3-pipe mode
setting configuration on my test machines. It does not make DPMS work,
so I still need to figure that out. As the DPMS paths are almost
entirely different from mode setting (whose crazy idea was that,
anyway?), that may take a bit
This is the complete set of patches that yield a working 3-pipe mode
setting configuration on my test machines. It does not make DPMS work,
so I still need to figure that out. As the DPMS paths are almost
entirely different from mode setting (whose crazy idea was that,
anyway?), that may take a bit
This is the complete set of patches that yield a working 3-pipe mode
setting configuration on my test machines. It does not make DPMS work,
so I still need to figure that out. As the DPMS paths are almost
entirely different from mode setting (whose crazy idea was that,
anyway?), that may take a bit
18 matches
Mail list logo
