You are not logged in.
Simple question that I can't seem to find the answer to...
There was a critical set of patches applied here that I've been waiting a year for:
https://bugzilla.kernel.org/show_bug.cgi?id=97941
As of Jan 11th, the patches were pushed to drm-intel-nightly.
I'm trying to figure out the release schedule of when this component gets pushed into the Linux mainline, and what version that would be for.
$ uname -r
4.3.3-3-ARCH
Bonus points for how to track a git commit revision from freedesktop all the way to the kernel(.org?) release.
Last edited by eduncan911 (2016-01-21 21:36:25)
Offline
From the bug report
Ping, anyone up for testing drm-intel-nightly again?
My plan is to close this bug as soon as I get confirmation that we no longer get a black screen.
Followed by responses on 2016-01-15 and 2016-01-16 indicating it appeared fixed.
So have you tried that tree using a revision on or after that data?
Mentioned in that bug report is this patch series http://patchwork.freedesktop.org/series/1998/
One of that patches can be found here http://cgit.freedesktop.org/drm-intel/c … 43d1b9b38c
From that patch the function with the following signature was added
static int goto_next_sequence_v3(const u8 *data, int index, int total)Now from https://git.kernel.org/cgit/linux/kerne … s/v4.5-rc1
That function is not present.
So if the above is correct it is not included in 4.5 so earliest inclusion would be 4.6.
Offline
Thanks!
Yep, I followed that chain of events as well - on the nightly builds.
The post title asked when does this "fix" was released to the mainline (e.g. 4.6, 4.7, etc?).
I agree. 4.6 is what it is looking like; but, how can one tell? You mentioned tracking a method signature which is, well, i guess possible. But no way to link commits/builds from drm-intel in the mainline trunk?
Offline
Thanks!
Yep, I followed that chain of events as well - on the nightly builds.
The post title asked when does this "fix" was released to the mainline (e.g. 4.6, 4.7, etc?).
I would check that that the issue is actually resolved in the nightly tree if you have not already done so or you could be spending months waiting for the patch to reach mainline only to find it does not work for you then.
As you can check from the mainline kernel tree the fixes are not there so how can anyone say when they will be there until they have been accepted and merged?
The subsystem maintainer may have a target release in mind for merging ( not that I suggest asking them if the information is not public ) but that is no guarantee it will appear in that release.
I agree. 4.6 is what it is looking like; but, how can one tell? You mentioned tracking a method signature which is, well, i guess possible. But no way to link commits/builds from drm-intel in the mainline trunk?
Seems likely there would be such a way but I am not aware of it.
Offline