From: jani.nikula@linux.intel.com (Jani Nikula)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/bridge: dw-hdmi: fix EDID parsing
Date: Thu, 09 Nov 2017 14:12:45 +0200 [thread overview]
Message-ID: <87efp7abwi.fsf@intel.com> (raw)
In-Reply-To: <CAEzXK1qx=frs=Py3FhUK2vCfEp3Uzt2Nt=hKyxOnaP-nj4z8HA@mail.gmail.com>
On Thu, 09 Nov 2017, Lu?s Mendes <luis.p.mendes@gmail.com> wrote:
> I've just applied the referred individual patch to kernel-4.14-rc5 and
> the EDID isn't loaded. dw-hdmi gets no firmware at all.
Sorry, I didn't mean you could just cherry-pick that one commit and make
it work. There were a number of preparatory patches before that, and I
think some cleanups on top.
Please try drm-next to make sure you have it all.
We didn't intend for the commits to be backported, instead we very much
wanted them to get a gradually increasing amount of exposure first to
make sure we don't break stuff.
And as I said elsewhere in the thread, Russell's patch may be relevant
for current Linus' master and stable. We just need to reconciliate how
the two things should work together in drm-next and v4.15 and on.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Luís Mendes" <luis.p.mendes@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
dri-devel@lists.freedesktop.org,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/bridge: dw-hdmi: fix EDID parsing
Date: Thu, 09 Nov 2017 14:12:45 +0200 [thread overview]
Message-ID: <87efp7abwi.fsf@intel.com> (raw)
In-Reply-To: <CAEzXK1qx=frs=Py3FhUK2vCfEp3Uzt2Nt=hKyxOnaP-nj4z8HA@mail.gmail.com>
On Thu, 09 Nov 2017, Luís Mendes <luis.p.mendes@gmail.com> wrote:
> I've just applied the referred individual patch to kernel-4.14-rc5 and
> the EDID isn't loaded. dw-hdmi gets no firmware at all.
Sorry, I didn't mean you could just cherry-pick that one commit and make
it work. There were a number of preparatory patches before that, and I
think some cleanups on top.
Please try drm-next to make sure you have it all.
We didn't intend for the commits to be backported, instead we very much
wanted them to get a gradually increasing amount of exposure first to
make sure we don't break stuff.
And as I said elsewhere in the thread, Russell's patch may be relevant
for current Linus' master and stable. We just need to reconciliate how
the two things should work together in drm-next and v4.15 and on.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-09 12:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:27 [PATCH] drm/bridge: dw-hdmi: fix EDID parsing Russell King
2017-11-07 11:27 ` Russell King
2017-11-09 6:49 ` Archit Taneja
2017-11-09 6:49 ` Archit Taneja
2017-11-09 8:23 ` Daniel Vetter
2017-11-09 8:23 ` Daniel Vetter
2017-11-09 9:31 ` Russell King - ARM Linux
2017-11-09 9:31 ` Russell King - ARM Linux
2017-11-09 9:49 ` Jani Nikula
2017-11-09 9:49 ` Jani Nikula
2017-11-09 9:51 ` Luís Mendes
2017-11-09 10:52 ` Luís Mendes
2017-11-09 10:52 ` Luís Mendes
2017-11-09 11:07 ` Luís Mendes
2017-11-09 11:07 ` Luís Mendes
2017-11-09 12:12 ` Jani Nikula [this message]
2017-11-09 12:12 ` Jani Nikula
2017-11-09 14:34 ` Luís Mendes
2017-11-09 14:34 ` Luís Mendes
2017-11-09 15:01 ` Jani Nikula
2017-11-09 15:01 ` Jani Nikula
2017-11-09 15:08 ` Luís Mendes
2017-11-09 15:22 ` Jani Nikula
2017-11-09 16:17 ` Daniel Vetter
2017-11-09 22:44 ` Luís Mendes
2017-11-10 9:37 ` Daniel Vetter
2017-11-09 16:28 ` Russell King - ARM Linux
2017-11-09 16:28 ` Russell King - ARM Linux
2017-11-09 18:45 ` Luís Mendes
2017-11-09 18:45 ` Luís Mendes
2017-11-09 16:26 ` Russell King - ARM Linux
2017-11-09 16:26 ` Russell King - ARM Linux
2017-11-10 9:45 ` Jani Nikula
2017-11-10 9:45 ` Jani Nikula
2017-11-09 8:27 ` Jani Nikula
2017-11-09 8:27 ` Jani Nikula
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=87efp7abwi.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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.