linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>,
	dri-devel@lists.freedesktop.org
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Dave Airlie <airlied@redhat.com>,
	C.Emde@osadl.org
Subject: Re: [PATCH 0/5] Fixes and additions to EDID generation
Date: Wed, 14 Nov 2018 12:49:11 +0200	[thread overview]
Message-ID: <8736s4j5nc.fsf@intel.com> (raw)
In-Reply-To: <20181113171053.is24iz65egl22aw7@xylophone.i.decadent.org.uk>

On Tue, 13 Nov 2018, Ben Hutchings <ben.hutchings@codethink.co.uk> wrote:
> This series adds two more EDIDs that I needed for a project some time ago,
> and fixes some problems that I found along the way.

See also [1]. The patches there have been applied via the linux-doc
tree.

> There isn't a listed maintainer for Documentation/EDID but it looks
> like it falls under the DRM umbrella.  Please let me know if this the
> wrong place.

Cc: linux-doc, Jon and Dave.

The Documentation/EDID directory was merged by Dave along with the EDID
firmware loader mechanism in da0df92b5731 ("drm: allow loading an EDID
as firmware to override broken monitor").

I think it would be reasonable to handle the EDID stuff via dri-devel
and the drm trees, and modify MAINTAINERS to reflect that. Thoughts?

(And in the long run we should use or write a tool to generate EDIDs
instead of using assembly with macros. And like Jon already mentioned in
the other thread, even the assembly probably shouldn't be under
Documentation. But I digress.)


BR,
Jani.

[1] http://mid.mail-archive.com/1541407715-5417-1-git-send-email-cniedermaier@dh-electronics.de

>
> Ben.
>
> Ben Hutchings (5):
>   drm: EDID: Remove a mess involving the number 63
>   drm: EDID: Fix bit masking of {X,Y}{OFFSET,PULSE}
>   drm: EDID: Don't force make to be silent
>   drm: EDID: Add a 1280x720 (720p) EDID
>   drm: EDID: Add a 1280x768 ("WXGA") EDID
>
>  Documentation/EDID/1024x768.S  |  4 ++--
>  Documentation/EDID/1280x1024.S |  4 ++--
>  Documentation/EDID/1280x720.S  | 45 ++++++++++++++++++++++++++++++++++++++++++
>  Documentation/EDID/1280x768.S  | 45 ++++++++++++++++++++++++++++++++++++++++++
>  Documentation/EDID/1600x1200.S |  4 ++--
>  Documentation/EDID/1680x1050.S |  4 ++--
>  Documentation/EDID/1920x1080.S |  4 ++--
>  Documentation/EDID/800x600.S   |  4 ++--
>  Documentation/EDID/HOWTO.txt   |  4 ++--
>  Documentation/EDID/Makefile    | 12 +++++------
>  Documentation/EDID/edid.S      | 10 ++++------
>  11 files changed, 114 insertions(+), 26 deletions(-)
>  create mode 100644 Documentation/EDID/1280x720.S
>  create mode 100644 Documentation/EDID/1280x768.S

-- 
Jani Nikula, Intel Open Source Graphics Center

       reply	other threads:[~2018-11-14 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181113171053.is24iz65egl22aw7@xylophone.i.decadent.org.uk>
2018-11-14 10:49 ` Jani Nikula [this message]
2018-11-21  9:35   ` [PATCH 0/5] Fixes and additions to EDID generation Daniel Vetter
2018-11-21 13:36     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736s4j5nc.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=C.Emde@osadl.org \
    --cc=airlied@redhat.com \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-doc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).