From: Chris Wilson <chris@chris-wilson.co.uk>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Adding 1080p modes to our TV Out mode list.
Date: Thu, 15 Dec 2011 16:06:47 +0000 [thread overview]
Message-ID: <f80fcd$2s35a8@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <CABVU7+uPCJkemGDg5DuTnTf2h0pddBtze9k_eGrhh_dKSie9Sw@mail.gmail.com>
On Thu, 15 Dec 2011 13:05:24 -0200, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> sorry... last email was unfinished and it was sent by mistake.. full version:
>
> For other patches in this serie the table can be found at our PRM
> http://intellinuxgraphics.org/VOL_3_display_registers_updated.pdf
>
> Section 5.2 TV Out Programming / 5.2.1 Television Standards / 5.2.1.1
> Timing Table
>
> However the 1080p was added on the new version witch is internal for now.
> I'm going to change the commit comment but I'm not happy with the
> comment such as:
>
> "Adding 1080p supported modes according to new PRM version which is
> internal for now."
>
> Because in a near future this document will be public and the comment
> will be there forever.
The comment can be updated to match the public material once it becomes
available (and more likely when someone finds something that needs
changing). If someone finds a reference to an internal document, they
are likely to ask us for it. At that point, we can double check whether
the material is now public, answer their question for them (and see if
we can improve the code so that the question becomes unncessary) or see
if we can provide them with the document under NDA.
Without a reference at all, that dialogue will never happen and we run
the risk of loosing the review. And more likely we will forget where to
find the information and have to search all the specs afresh. I'll trade
confusing a few people for saving time and preventing mistakes later.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-15 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 23:10 [PATCH 0/3] TV Out patches to make our mode list be according to TV timing standards Rodrigo Vivi
2011-12-14 23:10 ` [PATCH 1/3] drm/i915: Fix TV Out refresh rate Rodrigo Vivi
2012-01-06 18:11 ` Jesse Barnes
2012-01-06 22:02 ` Keith Packard
2012-01-16 14:10 ` Rodrigo Vivi
2011-12-14 23:10 ` [PATCH 2/3] drm/i915: Removing TV Out modes Rodrigo Vivi
2011-12-15 16:47 ` [PATCH 1/2] " Rodrigo Vivi
2012-01-06 18:11 ` [PATCH 2/3] " Jesse Barnes
2011-12-14 23:10 ` [PATCH 3/3] drm/i915: Adding 1080p modes to our TV Out mode list Rodrigo Vivi
2011-12-14 23:19 ` Chris Wilson
2011-12-15 15:00 ` Rodrigo Vivi
2011-12-15 15:05 ` Rodrigo Vivi
2011-12-15 16:06 ` Chris Wilson [this message]
2011-12-15 16:48 ` [PATCH 2/2] " Rodrigo Vivi
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='f80fcd$2s35a8@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.