From: Peter Clifton <peter.clifton@clifton-electronics.co.uk>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH] drm/i915: reinstate GM45 TV detection fix
Date: Tue, 27 Mar 2012 12:03:29 +0100 [thread overview]
Message-ID: <1332846209.25017.6.camel@localhost> (raw)
In-Reply-To: <CABVU7+s8PvQOfqad=49E-T_qGxm63Es5h2vL0sagA96w26HNLA@mail.gmail.com>
On Mon, 2012-03-26 at 15:57 -0300, Rodrigo Vivi wrote:
> The GM45 with tv-out is so rare machine that I never found one to test
> if this really cause regression and complete disable tv-out on gm45 so
> I'm in favor of apply this and when we find some one with gm45
> complaining about the tv-out not working we will be able to
> test/revert and find another fix for it. Meanwhile:
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Tested-by: Peter Clifton <Peter.Clifton@clifton-electronics.com>
I've been carrying that patch around in my own builds for my GM45 for
what feels like forever now (since before it was reverted... I helped
identify the requirement, by trial and error in the first place!).
For further details, you might like to contact the guy at Intel who
wrote the commit: ykzhao <yakui.zhao@intel.com>
>From some correspondence we had...
(Zhau)
> > > Yes. This is not consistent with the description on PRM.
> > > But this is required on Cantiga platform to make the TV detection
> > > reliable.
> >
> > Thanks Zhau,
(Me)
> > Hopefully we'll be able to get the patch re-committed to the
> kernel.
> >
> > Since the main issue with the patch was comments as to why this is a
> > good thing to do on GM45, would you be willing to create a new patch
> > with some code-comments (and commit message) explaining the source
> of
> > the correction?
> >
> > (Are there any comments from the BIOS code as to why these registers
> > need to be programmed in a particular way?)
(Zhau)
> Sorry that there is no comment in BIOS code. BIOS team only tells me
> to follow the BIOS code but there is no explanation about the reason.
(Me)
> > If you like, I could take your original patch and try to add some
> > comments along the lines of what you just explained, then re-send it
> > to intel-gfx for review.
Oops... I never got around to this.
I'd love to see it fixed though, but am too busy to chase it myself now.
Kind regards,
--
Peter Clifton <peter.clifton@clifton-electronics.co.uk>
Clifton Electronics
next prev parent reply other threads:[~2012-03-27 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 20:56 [PATCH] drm/i915: reinstate GM45 TV detection fix Daniel Vetter
2012-03-26 18:57 ` Rodrigo Vivi
2012-03-27 11:03 ` Peter Clifton [this message]
2012-03-27 11:14 ` 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=1332846209.25017.6.camel@localhost \
--to=peter.clifton@clifton-electronics.co.uk \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.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