From: Daniel Vetter <daniel@ffwll.ch>
To: Nicolae Rosia <nicolae.rosia.oss@gmail.com>
Cc: David Weinehall <tao@kernel.org>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: [Intel-gfx] i915 monitor hotplug on 4.1/4.4 PREEMPT
Date: Fri, 21 Oct 2016 14:27:56 +0200 [thread overview]
Message-ID: <20161021122756.GY20761@phenom.ffwll.local> (raw)
In-Reply-To: <CAKP5S=1Rb-Ees3TgeviXFdPfJqt3E0YwfRQKuyeumXAjM4bGOw@mail.gmail.com>
On Thu, Oct 20, 2016 at 05:09:52PM +0300, Nicolae Rosia wrote:
> Hi,
>
> On Thu, Oct 20, 2016 at 3:57 PM, David Weinehall <tao@kernel.org> wrote:
> >> > I get an udev event for unplugging, but there's no event generated for
> >> > plugging the monitor back in.
> >>
> >> Does it work on non-RT? Does it work on v4.8 or v4.9-rc1?
> >
> > The second one is relevant though. 4.1 is pre-historic, 4.4 is ancient.
> I just tested this on v4.8.2-rt2 and it works.
>
> Any tips on what I should do next, excluding the upgrade :-) ?
Very, very likely the answer is "upgrade", because:
$ git log --oneline v4.4..v4.8 -- drivers/gpu/drm/i915/ | wc -l
1931
That's not even counting the drm core changes, which also might be
relevant. Normally a revert bisect (to figure out the bugfix, hoping that
it's just 1 patch and not an entire series) would be an option. But since
-rt is still an add-on you'd need to rebase the entire -rt patchset every
time. That's impossible.
If you have way too much time, and know what you're doing another option
might be to backport all of drm (to avoid conflicts between drm core and
i915) from 4.8 to 4.4. No guarantee at all it'll work, and we generally
keep a few people busy for a while every time we have to do that
internally for some product team.
So yeah, "upgrade" is very likely is.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-10-21 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 12:15 i915 monitor hotplug on 4.1/4.4 PREEMPT Nicolae Rosia
2016-10-20 12:28 ` Jani Nikula
2016-10-20 12:57 ` David Weinehall
2016-10-20 14:08 ` [Intel-gfx] " Jani Nikula
2016-10-20 14:09 ` Nicolae Rosia
2016-10-21 12:27 ` Daniel Vetter [this message]
2016-10-21 13:21 ` Nicolae Rosia
2016-10-21 18: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=20161021122756.GY20761@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nicolae.rosia.oss@gmail.com \
--cc=tao@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox