All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Subject: Re: [PATCH v7 0/8] GEN-9 Arbitrated Bandwidth WM WA's & IPC
Date: Thu, 8 Dec 2016 16:12:37 +0000	[thread overview]
Message-ID: <1481213551.2375.34.camel@intel.com> (raw)
In-Reply-To: <20161208160051.dwurp2ft24ngetnj@phenom.ffwll.local>

Em Qui, 2016-12-08 às 17:00 +0100, Daniel Vetter escreveu:
> On Wed, Dec 07, 2016 at 05:35:09PM -0200, Paulo Zanoni wrote:
> > 
> > Em Qui, 2016-12-01 às 21:19 +0530, Mahesh Kumar escreveu:
> > > 
> > > This series implements following set of functionality
> > > 	Implement IPC WA's for Broxton/KBL
> > > 	Enable IPC in supported platforms
> > > 	Convert WM calculation to fixed point calculation
> > > 	Calculation of System memory Bandwidth for SKL/KBL/BXT
> > > 	Implementation of Arbitrated memory Bandwidth related WM WA's
> > 
> > Pushed patches 1, 2, 3, 5 and 6, with small bikesheds applied.
> > Thanks
> > for the patches!
> > 
> > (actually I had a little problem with dim, so right now only dinq
> > has
> > the patches, drm-tip doesn't, soon they will appear)
> 
> Hm, what did go boom with dim?

This was my first commit/push since the change. I had followed the
instructions on your email (including the dim setup stage), and then
when I did "dim push-queued" it complained that I didn't have the audio
remotes in my tree. After the error message I was not sure what was the
correct way to proceed.

I suppose we could change dim setup so that it really adds every single
remote that's needed? Also, why doesn't it just add the remotes itself?

>  If the pushing worked, then you can re-run
> just the drm-tip rebuilding with
> 
> $ dim rebuild-tip

Good to know, thanks for that.

> 
> Might also be worth it to upgrade to latest dim, we've dropped a few
> bugfixes in the branch push/pull logic in a few places since the big
> conversion, you might hit them.

I always upgrade to the latest version before using it.

> 
> If all this doesn't help, pls ping me on irc with a pastebin of
> what's
> going on. For testing you can always run

I sent you an email yesterday with the error message pasted... Maybe
you'll find it soon :).


> 
> $ dim pq
> 
> To repush dinq - dim will complain if you'll do a non-ff push and
> abort,
> so it's safe.
> -Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-12-08 16:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 15:49 [PATCH v7 0/8] GEN-9 Arbitrated Bandwidth WM WA's & IPC Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 1/8] drm/i915/skl: Add variables to check x_tile and y_tile Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 2/8] drm/i915/bxt: IPC WA for Broxton Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 3/8] drm/i915/kbl: IPC workaround for kabylake Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 4/8] drm/i915/bxt: Enable IPC support Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 5/8] drm/i915/skl+: change WM calc to fixed point 16.16 Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 6/8] drm/i915: Add intel_atomic_get_existing_crtc_state function Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 7/8] drm/i915: Decode system memory bandwidth Mahesh Kumar
2016-12-08 23:55   ` Paulo Zanoni
2017-02-15 15:00     ` Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 8/8] drm/i915/gen9: WM memory bandwidth related workaround Mahesh Kumar
2016-12-15 17:07   ` Paulo Zanoni
2017-02-15 15:00     ` Mahesh Kumar
2016-12-01 16:15 ` ✓ Fi.CI.BAT: success for GEN-9 Arbitrated Bandwidth WM WA's & IPC (rev3) Patchwork
2016-12-07 19:35 ` [PATCH v7 0/8] GEN-9 Arbitrated Bandwidth WM WA's & IPC Paulo Zanoni
2016-12-08 16:00   ` Daniel Vetter
2016-12-08 16:12     ` Zanoni, Paulo R [this message]
2016-12-08 16:18       ` 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=1481213551.2375.34.camel@intel.com \
    --to=paulo.r.zanoni@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@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 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.