From: "Kalamarz, Lukasz" <lukasz.kalamarz@intel.com>
To: "Dec, Katarzyna" <katarzyna.dec@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 2/5] lib/gen6_render.h: Use gen6 definitions where it is possible
Date: Mon, 11 Jun 2018 12:46:26 +0000 [thread overview]
Message-ID: <1528721184.4203.57.camel@intel.com> (raw)
In-Reply-To: <20180611074434.GF8119@kdec5-desk.ger.corp.intel.com>
On Mon, 2018-06-11 at 09:44 +0200, Katarzyna Dec wrote:
> On Fri, Jun 08, 2018 at 01:38:52PM +0200, Lukasz Kalamarz wrote:
> I think lib/gen6_render.h header is not for this patch.
> And with adding new header title needs to be changed I guess.
>
> (this header confused my when I started to do a review on Fri - I
> thought
> that changes are made in gen6_render :) )
>
My bad, will fix that.
> I would also changed commit msg, maybe sth like this:
> > As long as it is applicable, We should use in our libs
> > definitions from oldest gen if it is possible.
>
> When using genX_render definitions, we should use the oldest
> definition it
> is possible.
>
Will fix that in next version.
> > This patch
> > reuse gen6 definitons if registers/fields/shifts that were
> > reintroduced in other genX_render headers.
> >
> > Signed-off-by: Lukasz Kalamarz <lukasz.kalamarz@intel.com>
> > Cc: Katarzyna Dec <katarzyna.dec@intel.com>
> > Cc: Antonio Argenziano <antonio.argenziano@intel.com>
> > Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> > Cc: Ewelina Musial <ewelina.musial@intel.com>
> > ---
> > lib/rendercopy_gen7.c | 108 +++++++++++++-
> > ------------
> > lib/rendercopy_gen8.c | 4 +-
> > lib/rendercopy_gen9.c | 4 +-
> > tools/null_state_gen/intel_renderstate_gen7.c | 108 +++++++++++++-
> > ------------
> > tools/null_state_gen/intel_renderstate_gen8.c | 10 +--
> > tools/null_state_gen/intel_renderstate_gen9.c | 10 +--
> > 6 files changed, 122 insertions(+), 122 deletions(-)
> >
> > diff --git a/lib/rendercopy_gen7.c b/lib/rendercopy_gen7.c
> > index 82e33288..bdcf3c7b 100644
> > --- a/lib/rendercopy_gen7.c
> > +++ b/lib/rendercopy_gen7.c
> > @@ -101,35 +101,35 @@ gen7_bind_buf(struct intel_batchbuffer
> > *batch,
> > static void
> > gen7_emit_vertex_elements(struct intel_batchbuffer *batch)
> > {
> > - OUT_BATCH(GEN7_3DSTATE_VERTEX_ELEMENTS |
> > + OUT_BATCH(GEN6_3DSTATE_VERTEX_ELEMENTS |
> > ((2 * (1 + 2)) + 1 - 2));
> >
> > - OUT_BATCH(0 << GEN7_VE0_VERTEX_BUFFER_INDEX_SHIFT |
> > GEN7_VE0_VALID |
> > - SURFACEFORMAT_R32G32B32A32_FLOAT <<
> > GEN7_VE0_FORMAT_SHIFT |
> > - 0 << GEN7_VE0_OFFSET_SHIFT);
> > + OUT_BATCH(0 << VE0_VERTEX_BUFFER_INDEX_SHIFT | VE0_VALID |
> > + SURFACEFORMAT_R32G32B32A32_FLOAT <<
> > VE0_FORMAT_SHIFT |
> > + 0 << VE0_OFFSET_SHIFT);
>
> Why GENX_prefix was removed from SURFACEFORMAT_R32G32B32A32_FLOAT (in
> already
> merged patches), but this prefix is still in
> e.g.GEN6_3DSTATE_VERTEX_ELEMENTS?
> This is only a question for a reason, not a suggestion :)
Surface formats were not changing, but some registers/fields/shifts
changed their definitions across gens. This is why I believe we should
stay with this naming convention.
>
> Kasia :)
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-06-11 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 11:38 [igt-dev] [PATCH i-g-t 1/5] lib/gen7_render: include gen6_render header Lukasz Kalamarz
2018-06-08 11:38 ` [igt-dev] [PATCH i-g-t 2/5] lib/gen6_render.h: Use gen6 definitions where it is possible Lukasz Kalamarz
2018-06-11 7:44 ` Katarzyna Dec
2018-06-11 12:46 ` Kalamarz, Lukasz [this message]
2018-06-11 13:40 ` Katarzyna Dec
2018-06-08 11:38 ` [igt-dev] [PATCH i-g-t 3/5] lib/gen7_render: Drop duplicated definitions Lukasz Kalamarz
2018-06-08 11:38 ` [igt-dev] [PATCH i-g-t 4/5] lib/gen8_render: Cleanup of libs Lukasz Kalamarz
2018-06-11 7:58 ` Katarzyna Dec
2018-06-11 12:50 ` Kalamarz, Lukasz
2018-06-11 13:38 ` Katarzyna Dec
2018-06-08 11:38 ` [igt-dev] [PATCH i-g-t 5/5] lib/gen9_render: Header cleanup Lukasz Kalamarz
2018-06-11 7:59 ` Katarzyna Dec
2018-06-08 12:16 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] lib/gen7_render: include gen6_render header Patchwork
2018-06-08 14:52 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-06-11 7:31 ` [igt-dev] [PATCH i-g-t 1/5] " Katarzyna Dec
2018-06-11 12:42 ` Kalamarz, Lukasz
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=1528721184.4203.57.camel@intel.com \
--to=lukasz.kalamarz@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=katarzyna.dec@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