On Tue, Nov 14, 2017 at 1:32 PM, Ville Syrjala
<ville.syrj...@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrj...@linux.intel.com>
>
> These days DRM_MODE_TYPE_USERDEF is used to flag modes defined via the
> kernel command line. Update the docs to reflect that fact.
>
> Signed-off-by: Ville Syrjälä <ville.syrj...@linux.intel.com>
Acked-by: Alex Deucher <alexander.deuc...@amd.com>
> ---
> include/drm/drm_modes.h | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/include/drm/drm_modes.h b/include/drm/drm_modes.h
> index 09773e766e1f..8ddf7adb98df 100644
> --- a/include/drm/drm_modes.h
> +++ b/include/drm/drm_modes.h
> @@ -253,6 +253,7 @@ struct drm_display_mode {
> * - DRM_MODE_TYPE_DRIVER: Mode created by the driver, which is all
> of
> * them really. Drivers must set this bit for all modes they create
> * and expose to userspace.
> + * - DRM_MODE_TYPE_USERDEF: Mode defined via kernel command line
> *
> * Plus a big list of flags which shouldn't be used at all, but are
> * still around since these flags are also used in the userspace ABI:
> @@ -262,9 +263,6 @@ struct drm_display_mode {
> * - DRM_MODE_TYPE_CLOCK_C and DRM_MODE_TYPE_CRTC_C: Define leftovers
> * which are stuck around for hysterical raisins only. No one has
> an
> * idea what they were meant for. Don't use.
> - * - DRM_MODE_TYPE_USERDEF: Mode defined by userspace, again a
> vestige
> - * from older kms designs where userspace had to first add a custom
> - * mode to the kernel's mode list before it could use it. Don't
> use.
> */
> unsigned int type;
>
> --
> 2.13.6
>
> _______________________________________________
> dri-devel mailing list
> dri-de...@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
