From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] omapdrm/N900 display broken
Date: Fri, 27 Nov 2020 15:10:48 +0200 [thread overview]
Message-ID: <8010e452-745a-ac12-bc02-5537305c70ed@gmail.com> (raw)
In-Reply-To: <1fe9fed7-f619-eb6a-6e31-b9eadbf09bad@ti.com>
On 27.11.20 г. 13:45 ч., Tomi Valkeinen wrote:
> On 27/11/2020 01:17, Ivaylo Dimitrov wrote:
>> Hi Tomi,
>>
>> On 26.11.20 г. 16:11 ч., Tomi Valkeinen wrote:
>>> Hi Aaro, Ivaylo,
>>>
>>> On 24/11/2020 23:03, Ivaylo Dimitrov wrote:
>>>
>>>> Is there any progress on the issue? I tried 5.9.1 and still nothing displayed.
>>>
>>> Can you test the attached patch?
>>>
>>
>> With this patch I don't see oops that Aaro reported, so:
>>
>> Tested-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
>>
>> Seems to fix the particular issue, however, now we get another oops. As this is not upstream kernel
>> but one with PVR related patches, I will try again with vanilla 5.9.
>>
>> Just in case oops rings any bells (the line in question is
>> https://github.com/maemo-leste/droid4-linux/blob/maemo-5.9/drivers/gpu/drm/omapdrm/omap_gem.c#L801)
>
> Do the PVR patches touch omapdrm? The call stack looks like normal boot time probing stuff, not
> something happening later (possibly from PVR).
>
pvr driver is not even enabled in that particular config, however, I see
"HACK: drm/omap: Add omapdrm plugin API" patch in the tree that touches
omap-gem.c, I don't really want to just create some noise for problems
that are created by out-of-tree patches. And yeah, it looks like a
normal boot time probing stuff. As soon as I have some spare time
(hopefully later today) I will try vanilla 5.9.x with
omap2plus_defconfig and will report.
Ivo
next prev parent reply other threads:[~2020-11-27 13:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 18:14 Aaro Koskinen
2020-08-04 12:13 ` Tomi Valkeinen
2020-08-04 12:39 ` Tomi Valkeinen
2020-08-23 16:26 ` Aaro Koskinen
2020-08-25 13:16 ` Tomi Valkeinen
2020-11-24 21:03 ` Ivaylo Dimitrov
2020-11-26 14:11 ` Tomi Valkeinen
2020-11-26 23:17 ` Ivaylo Dimitrov
2020-11-27 11:45 ` Tomi Valkeinen
2020-11-27 13:10 ` Ivaylo Dimitrov [this message]
2020-11-27 15:37 ` Ivaylo Dimitrov
2020-11-27 17:30 ` Tomi Valkeinen
2020-11-27 18:44 ` Ivaylo Dimitrov
2020-11-25 9:07 ` Daniel Vetter
2020-11-27 8:43 ` Tomi Valkeinen
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=8010e452-745a-ac12-bc02-5537305c70ed@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®