Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chad Versace <chad.versace@linux.intel.com>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: s/valleyview/baytrail
Date: Fri, 10 May 2013 08:53:10 -0700	[thread overview]
Message-ID: <518D17E6.20405@linux.intel.com> (raw)
In-Reply-To: <1368075212-6631-1-git-send-email-ben@bwidawsk.net>

On 05/08/2013 09:53 PM, Ben Widawsky wrote:
> Bay Trail is the marketing name for the new Silvermont based SOCs we've
> been calling Valleyview. All recent Intel disclosed documents use the
> term "Bay Trail." AFAICT, only leaked docs (and our code) use the term
> Valleyview. I've also verified with internal sources that references to,
> "Valleyview" should be dropped.
>
> Why?
> We've always strived to make the already confusing generation
> information as clear as possible in our driver. With the introduction
> of the below, we made two names referring to the exact same silicon.
>
> commit 93c34e70ebf464a9ee142d93b681c5df094ec654
> Author: Kenneth Graunke <kenneth@whitecape.org>
> Date:   Mon Apr 22 00:53:50 2013 -0700
>
>      drm/i915: Fix page table entries for Bay Trail.
>
> While it's tempting to simply do the renames in Ken's patch, it's simply
> not correct. As an added bonus, Mesa also uses the byt/baytrail names.
>
> Yes. I know this is painful. Doing it now is the least painful way to do
> this right (short of going back in time.)
>
> disclaimer: only compile tested.
> disclaimer2: I didn't fix pre-existing checkpatch issues.
>
> CC: Kenneth Graunke <kenneth@whitecape.org>
> CC: Jesse Barnes <jbarnes@virtuousgeek.org>
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>

Acked-by: Chad Versace <chad.versace@linux.intel.com>

      parent reply	other threads:[~2013-05-10 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  4:53 [PATCH] drm/i915: s/valleyview/baytrail Ben Widawsky
2013-05-09  5:17 ` Kenneth Graunke
2013-05-10 15:53 ` Chad Versace [this message]

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=518D17E6.20405@linux.intel.com \
    --to=chad.versace@linux.intel.com \
    --cc=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.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