From: David Weinehall <david.weinehall@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/3] HDMI optimization series
Date: Wed, 12 Aug 2015 14:55:55 +0300 [thread overview]
Message-ID: <20150812115555.GM6150@boom> (raw)
In-Reply-To: <20150811094142.GM17734@phenom.ffwll.local>
On Tue, Aug 11, 2015 at 11:41:42AM +0200, Daniel Vetter wrote:
> On Mon, Aug 10, 2015 at 02:05:47PM +0530, Jindal, Sonika wrote:
> >
> >
> > On 8/10/2015 1:38 PM, Daniel Vetter wrote:
> > >On Mon, Aug 10, 2015 at 04:50:37AM +0000, Jindal, Sonika wrote:
> > >>Hi Daniel,
> > >>
> > >>That patch was already merged:
> > >>http://lists.freedesktop.org/archives/intel-gfx/2015-July/071142.html
> > >>
> > >>For SKL, the above patch helped in getting the correct ISR bits set.
> > >>One option is to enable the HDMI optimization from VLV onwards.
> > >>I don't have an ivb machine to try out the issue.
> > >
> > >ivb is simple the machine I have here, but when we tried this the last
> > >time around we had reports for all platforms (your patch still doesn't
> > >cite the relevant sha1 btw). I think there are 3 possible explanations:
> > >
> > Yes, I don't know which were those patches and how to find them..
>
> git blame (recursively) and git log on intel_hdmi.c will tell you the
> story. I require all these extensive git commit messages because I dig
> them out daily. Also git log --pickaxe (well I use the equivalent in the
> gitk gui). If these tools are generally unknown in the vpg display team
> then we absolutely need to do a training session about them, they're
> extremely powerful and useful to dig out the history of the i915 code.
git blame I use a lot to find whom to ask for clarification.
pickaxe, however, was new to me. Thanks for the tip, will look into it.
As far as training sessions about git goes, I think a lot of people could
benefit from it; git has a LOT of hidden gems, and it seems almost
everyone has different workflows.
Kind regards, David
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-08-12 11:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 11:51 [PATCH 0/3] HDMI optimization series Sonika Jindal
2015-07-14 11:51 ` [PATCH 1/3] drm/i915: add attached connector to hdmi container Sonika Jindal
2015-07-14 11:51 ` [PATCH 2/3] drm/i915: Add HDMI probe function Sonika Jindal
2015-07-14 11:51 ` [PATCH 3/3] drm/i915: Check live status before reading edid Sonika Jindal
2015-07-14 14:29 ` Imre Deak
2015-07-15 3:55 ` Jindal, Sonika
2015-08-05 10:02 ` Imre Deak
2015-08-10 5:44 ` Sivakumar Thulasimani
2015-08-17 5:39 ` Jindal, Sonika
2015-08-07 13:23 ` [PATCH 0/3] HDMI optimization series Daniel Vetter
2015-08-10 4:50 ` Jindal, Sonika
2015-08-10 8:08 ` Daniel Vetter
2015-08-10 8:35 ` Jindal, Sonika
2015-08-11 9:41 ` Daniel Vetter
2015-08-11 11:03 ` Sharma, Shashank
2015-08-12 12:25 ` Daniel Vetter
2015-08-12 12:34 ` Sharma, Shashank
2015-08-12 12:40 ` Daniel Vetter
2015-08-12 12:46 ` Sharma, Shashank
2015-08-12 11:55 ` David Weinehall [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=20150812115555.GM6150@boom \
--to=david.weinehall@linux.intel.com \
--cc=daniel@ffwll.ch \
--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 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.