From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 4/4] drm/i915: Add PSR docbook
Date: Wed, 12 Nov 2014 17:07:19 +0100 [thread overview]
Message-ID: <20141112160719.GB25711@phenom.ffwll.local> (raw)
In-Reply-To: <CABVU7+sRkFM2KAb+muvaQ1h3WYRf5edmu5c8G8Kp8_Wpes-M7A@mail.gmail.com>
On Wed, Nov 12, 2014 at 08:00:26AM -0800, Rodrigo Vivi wrote:
> I believe that on docs that is visible to end users we could use more
> market names besides the codenames.
This isn't documentation for end users but developers working on i915. So
aligning with the codenames used in the driver is more important imo than
aligning with marketing. We could do an overview section in the docs to
match up marketing names with codenames in the driver (or explain stuff
like what IS_VALLEYVIEW means ...). Or just do a link to wikipedia, since
that page is usually really accurate ;-)
But imo that should be pulled together into a separate section.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-11-12 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 23:55 [PATCH 1/4] drm/i915: HSW/BDW PSR Set idle_frames = VBT + 1 Rodrigo Vivi
2014-11-07 23:55 ` [PATCH 2/4] drm/i915: Make dp aux pack/unpack public outside intel_dp.c Rodrigo Vivi
2014-11-07 23:55 ` [PATCH 3/4] drm/i915: Introduce intel_psr.c Rodrigo Vivi
2014-11-07 23:55 ` [PATCH 4/4] drm/i915: Add PSR docbook Rodrigo Vivi
2014-11-12 9:16 ` Daniel Vetter
2014-11-12 16:00 ` Rodrigo Vivi
2014-11-12 16:07 ` Daniel Vetter [this message]
2014-11-12 9:00 ` [PATCH 1/4] drm/i915: HSW/BDW PSR Set idle_frames = VBT + 1 Daniel Vetter
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=20141112160719.GB25711@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.com \
--cc=rodrigo.vivi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox