Hi Dave and Daniel,
here goes couple display fixes for this last round of fixes before -rc1
drm-intel-next-fixes-2020-10-15:
- Set all unused color plane offsets to ~0xfff again (Ville)
- Fix TGL DKL PHY DP vswing handling (Ville)
The following changes since commit
Hi Dave and Daniel,
Here goes our first next-fixes. Please be aware this includes
both drm-intel-next and drm-intel-gt-next.
Also, most of patches from drm-intel-gt-next were accumulated
for not being part of current drm-intel-fixes flow while we
are defining the new split and flow.
So, there
Hi Dave and Daniel,
here goes our last pull request targeting 5.10.
drm-intel-next-2020-09-17:
Driver Changes:
- Reduce INTEL_DISPLAY_ENABLED to just removed outputs treating it as
disconnected (Ville)
- Introducing new AUX, DVO, and TC ports and refactoring code around hot plug
interrupts
Hi Dave and Daniel,
here goes the first pull request towards 5.10:
As requested, the gem patches have been separated into
a drm-intel/topic/drm-intel-gem-next that will be sent separately
by the gem team later.
Thanks,
Rodrigo.
drm-intel-next-2020-08-24-1:
UAPI Changes:
- Introduce a
On Mon, 10 Aug 2020, Dave Airlie wrote:
> Like this stuff has been getting past me for years but I'm not happy
> about it anymore, I'm going to just be grumpy asshole going forward.
> If we introduced scheduler races in linux-next, I want to see reverts,
> and reverts only until we stopped
On Fri, 31 Jul 2020 at 02:26, Joonas Lahtinen
wrote:
>
> Hi Dave & Daniel,
>
> (Covering for Jani here for drm-intel-next-fixes)
>
> 5 new commits over drm-intel-next here.
>
> Fix for KASAN detected race condition and linux-next scheduler
> WARNs. Patch to avoid IRQ spinlock and Cc: stable PMU
Hi Dave & Daniel,
(Covering for Jani here for drm-intel-next-fixes)
5 new commits over drm-intel-next here.
Fix for KASAN detected race condition and linux-next scheduler
WARNs. Patch to avoid IRQ spinlock and Cc: stable PMU refcount
update.
CI machinery needed some kicking, so results didn't
On Wed, Jul 15, 2020 at 3:34 PM Jani Nikula wrote:
>
>
> Argh, failed to mention:
>
> On Wed, 15 Jul 2020, Jani Nikula wrote:
> > Lee Shawn C (1):
> > drm/i915/mst: filter out the display mode exceed sink's capability
>
> The above depends on:
>
> > Lyude Paul (1):
> >
Argh, failed to mention:
On Wed, 15 Jul 2020, Jani Nikula wrote:
> Lee Shawn C (1):
> drm/i915/mst: filter out the display mode exceed sink's capability
The above depends on:
> Lyude Paul (1):
> drm/probe_helper: Add drm_connector_helper_funcs.mode_valid_ctx
Which has changes
Hi Dave & Daniel -
The 2nd and presumably the last i915 feature pull for v5.9.
drm-intel-next-2020-07-15:
drm/i915 features for v5.9, batch #2
Highlights:
- Very early DG1 enabling (Abdiel, Lucas, Anusha)
Gem/GT:
- Fix spinlock recursion on signaling a signaled request (Chris)
- Perf: Use GTT
Hi Dave & Daniel -
Here's the first batch of i915 features for v5.9.
BR,
Jani.
drm-intel-next-2020-07-02:
drm/i915 features for v5.9
Highlights:
- Rocket Lake (RKL) platform enabling (Matt Roper, Lucas, José, Aditya)
Gem/GT:
- Numerous selftest fixes and improvements (Chris)
- TGL, RKL,
Quoting Joonas Lahtinen (2020-06-10 12:37:00)
> Hi Dave & Daniel,
>
> Sending this one early for it to hopefully make it in before -rc1.
>
> Two important fixes: OOPS fix that was missing "Fixes:" tag and
> not picked up earlier. Also fix for a use-after-free in cmdparser.
>
> Additional fixup
Hi Dave & Daniel,
Sending this one early for it to hopefully make it in before -rc1.
Two important fixes: OOPS fix that was missing "Fixes:" tag and
not picked up earlier. Also fix for a use-after-free in cmdparser.
Additional fixup to module param types.
Regards, Joonas
***
Hi Dave & Daniel,
Fixes use-after free on display global state tracking.
Then the removal of write bits from sysfs files
where changed value is not reflected anywhere.
Two scheduler fixes with deps that are Cc: stable.
Includes the GVT pull which has two build warning fixes
at this time.
Hi Dave & Daniel,
Two bigger fixes to corner case kernel access faults
and three workload scheduling fixups this week.
CI_DINF_191 at:
https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html?
I got gvt-next-fixes pull today, I'll pull it next week so it
has time to run through
Hi Dave & Daniel,
On top of the drm-intel-next PR one fix for TypeC mode resets and
two compile time warning fixes.
CI results for your viewing:
https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html
CI_DINF_189 = drm-intel-next pull
CI_DINF_190 = this pull (3 patches)
There
Hi Dave & Daniel,
Here's the last batch heading to v5.8. Indeed a lot of
enabling and fixes building on the previous prepping.
One cross-subsystem patch to video/hdmi for DRM infoframe
unpacking. One sysfs patch to add readout and ability to
restore of kernel compilation time default engine
Quoting Dave Airlie (2020-05-14 04:28:17)
> On Thu, 14 May 2020 at 03:10, Joonas Lahtinen
> wrote:
> >
> > Ping for merging this? If there are no issues, I'd prefer to pull in
> > next gvt-next and tag the final pull sooner than later.
>
> Can you check that I'm correct and this isn;'t in
On Thu, 14 May 2020 at 03:10, Joonas Lahtinen
wrote:
>
> Ping for merging this? If there are no issues, I'd prefer to pull in
> next gvt-next and tag the final pull sooner than later.
Can you check that I'm correct and this isn;'t in patchwork. I've
checked both the dri-devel and intel-gfx
Ping for merging this? If there are no issues, I'd prefer to pull in
next gvt-next and tag the final pull sooner than later.
Regards, Joonas
Quoting Joonas Lahtinen (2020-04-30 15:49:04)
> Hi Dave & Daniel,
>
> Fix for performance regression GitLab #1698: Iris Plus 655 and
> 4K screen. Missing
Hi Dave & Daniel,
Fix for performance regression GitLab #1698: Iris Plus 655 and
4K screen. Missing workarounds for Tigerlake, and a fix for
DP display audio WA. Unbreaking enable_dpcd_backlight, fixes
to power code for Icelake+.
Improvements to the soft-RC6 code to improve power efficiency,
a
Hi Dave & Daniel,
This pull contains a backmerge of drm-next and pulls the phy-compliance
branch from Maarten.
On the uAPI front, drop some machine generated perf OA configs from
915 now that they mostly passed from userspace. Add new perf OA interfaces
to limit CPU overhead and to allow
Hi Dave and Daniel,
Couple display fixes, including vswing table and display TypeC
port in TBT mode fix for ICL+
A few GT/GEM alloc/reloc fixes with one to flush all the
reloc_gpu batch which has cc:stable #5.2
Here goes drm-intel-next-fixes-2020-04-08:
- Flush all the reloc_gpu batch (Chris)
-
Hi Dave and Daniel,
Here goes drm-intel-next-fixes-2020-04-02:
Only gvt fixes on this round:
- Fix non-privilege access warning (Tina)
- Fix display port type (Tina)
- BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
- Bypass length check of LRI (Yan)
- Fix one klocwork warning (Tina)
Thanks,
Hi Dave and Daniel,
Here goes drm-intel-next-fixes-2020-03-27:
Fixes for instability on Baytrail and Haswell;
Ice Lake RPS; Sandy Bridge RC6; and few others around
GT hangchec/reset; livelock; and a null dereference.
Thanks,
Rodrigo.
The following changes since commit
Hi Dave and Daniel,
Here goes drm-intel-next-2020-03-13:
UAPI Changes:
On i915 we have a new UAPI to allow userspace to specify CS ring buffer size on
construction (I915_CONTEXT_PARAM_RINGSIZE) and also new sysfs entries exposing
various engine properties
GVT Changes:
On GVT we have VFIO edid
Hi Dave and Daniel,
I do regret for taking so long for this first pull request.
It accumulated over 400 patches with many code refactors, specially around
gpu hangs detection/recover/debugability; display watermark handling;
drm logs and warns; and our display conversion to use drm_i915_private
Hi Dave & Daniel -
Most of these were aimed at a "next fixes" pull already during the merge
window, but there were issues with the baseline I used, which resulted
in a lot of issues in CI. I've regenerated this stuff piecemeal now,
adding gradually to it, and it seems healthy now.
Due to the
On Tue, 14 Jan 2020, Chris Wilson wrote:
> Quoting Jani Nikula (2020-01-14 11:43:22)
>>
>> Hi Dave & Daniel -
>>
>> Last batch for v5.6, slightly delayed I'm afraid.
>
> I'd like to close https://gitlab.freedesktop.org/drm/intel/issues/738
> for 5.6, otherwise we'll have some more nasty emails
Quoting Jani Nikula (2020-01-14 11:43:22)
>
> Hi Dave & Daniel -
>
> Last batch for v5.6, slightly delayed I'm afraid.
I'd like to close https://gitlab.freedesktop.org/drm/intel/issues/738
for 5.6, otherwise we'll have some more nasty emails from bewildered
users/devs.
Hi Dave & Daniel -
Last batch for v5.6, slightly delayed I'm afraid.
drm-intel-next-2020-01-14:
Final drm/i915 features for v5.6:
- DP MST fixes (José)
- Fix intel_bw_state memory leak (Pankaj Bharadiya)
- Switch context id allocation to xarray (Tvrtko)
- ICL/EHL/TGL workarounds (Matt Roper,
Hi Dave & Daniel -
The first, and huge, i915 feature pull for v5.6. We really need to fix
dim to allow continuous tagging, and properly handle multiple tags in a
single pull request. Writing changelogs for pulls like this becomes
daunting.
Consequently, the changelog below is more like a
Hi Dave & Daniel,
Final one for 5.5-rc1.
A fix for EHL port D programming (DDI-D) and a couple of CI
fixes for GEM contexts.
This includes the GVT fixes PR with one command parser fix and
one WARN splat fix.
Regards, Joonas
***
drm-intel-next-fixes-2019-12-05:
- Includes
Hi Dave & Daniel,
Most importantly we have the fix to power regression that was
introduced by the security fixes. Then fix for query uAPI and
increase in request pre-emption timeout to accommodate super
heavy benchmarks.
Couple of display voltage programming fixes too.
Thanks to Chris for
Hi Dave & Daniel,
A quick fixup amendment to the previous PR. gem_exec_reloc/basic-range
got broken in CI, so we've issued a patch revert the offending commit
for now.
Once the results for CI_DINF_163 appear here, and the timeouts seen
in last three CI_DINF_ are green, feel free to pull this:
Quoting Joonas Lahtinen (2019-11-20 22:40:35)
> Hi Dave & Daniel,
>
> NOTE: CI shard results are delayed, bu I'm sending this
> already because I'll travel tomorrow. I'll let you know
> if the results look OK or not. Or you can look up
> CI_DINF_162 results check at:
>
>
Hi Dave & Daniel,
NOTE: CI shard results are delayed, bu I'm sending this
already because I'll travel tomorrow. I'll let you know
if the results look OK or not. Or you can look up
CI_DINF_162 results check at:
https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html
This was
Hi Dave & Daniel,
Here comes the set of fixes for drm-intel-next. Quite a few fixes
after a silent last week.
I'll do the backmerge of the BCX fixes from Linus's tree next and
send it as an extra PR.
Regards, Joonas
***
drm-intel-next-fixes-2019-11-14:
- PMU "Frequency" is reported as
Hi Dave & Daniel,
A quiet start. Hopefully stays that way :)
RCU tracking fix and suspend GEM_BUG_ON fix with dependencies.
Regards, Joonas
***
drm-intel-next-fixes-2019-11-07:
One RCU fix and fix for suspend GEM_BUG_ON (with dependencies).
The following changes since commit
Hi Dave & Daniel,
Here goes the final feature pull request for 5.5.
Adding a new uAPI to support cleanup of long running workloads
when process is killed.
Adds fake lmem region code under DRM_I915_UNSTABLE Kconfig
protection to make iGFX behave like local memory device. For
testing
Hi Dave & Daniel,
Another feature pull, I'll send the final one next week.
New uAPI for OA features to support VK_INTEL_performance_query,
Mesa changes are at:
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/932
Fixes for black/blue screen issues, Tigerlake enabling,
HDR for DP
Hi Dave & Daniel,
Back from XDC, so here comes the first bunch of features.
For uAPI: immutable zpos plane property added, disallow
userptr import of GGTT mmapped buffer and disallow tiling
Other than that loads of early Tigerlake enabling and many
Icelake fixups. DP MST and PSR fixes as well
Hi Dave and Daniel,
This should've gone out yesterday, but apparently I had some issue with my mutt
here.
Anyway, nothing that couldn't wait for rc2
Here goes drm-intel-next-fixes-2019-09-26:
- Fix concurrence on cases where requests where getting retired at same time as
resubmitted to HW
-
Hi Dave and Daniel,
Here goes drm-intel-next-fixes-2019-09-19:
- Extend old HSW workaround to fix some GPU hangs on Haswell GT2
- Fix return error code on GEM mmap.
- White list a chicken bit register for push constants legacy mode on Mesa
- Fix resume issue related to GGTT restore
- Remove
Hi Dave and Daniel,
Here goes drm-intel-next-fixes-2019-09-11:
Few fixes on GGTT and PPGTT around pin, locks, fence and vgpu.
This also includes GVT fixes with two recent fixes:
one for recent guest hang regression and another for guest reset fix.
Thanks,
Rodrigo.
The following changes since
Hi Dave and Daniel,
Here goes the final pull request targeting 5.4.
It's important to highlight that we got a conflict on a backmerge yesterday
which had already been solved on linux-next with a fix up patch:
From: Stephen Rothwell
Date: Wed, 14 Aug 2019 12:48:39 +1000
Subject: [PATCH] drm:
Hi Dave and Daniel,
(atempt v2:
for some reason my dim didn't recognized the path apparently
)
Here goes the final pull request targeting 5.4.
It's important to highlight that we got a conflict on a backmerge yesterday
which had already been solved on linux-next with a fix up patch:
From:
On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi wrote:
>
> Hi Dave and Daniel,
>
> Here goes the final pull request targeting 5.4.
For some reason patchwork hasn't picked this up. or if it has I can't
see it. Not sure whether it was the earlier patch code in it or
something else malformed.
Dave.
Hi Dave and Daniel,
Here goes the first pull request targeting 5.4.
It mostly comes with a lot of platform enabling patches and reworks
and simplification around locking mechanisms, ppgtt allocation, engines
and intel_gt in general.
There were 2 silent backmerges that should be transparent for
Hi Dave & Daniel, final i915 feature pull for v5.3.
While I'll follow up with i915 fixes leading to the v5.3 release, I'll
pass the drm-intel-next baton to Rodrigo who'll take care of v5.4.
BR,
Jani.
drm-intel-next-2019-06-19:
Features:
- HDR support (Uma, Ville)
- Add I2C symlink under HDMI
Hi Dave, Daniel -
First i915 feature pull for v5.3.
BR,
Jani.
drm-intel-next-2019-05-24:
Features:
- Engine discovery query (Tvrtko)
- Support for DP YCbCr4:2:0 outputs (Gwan-gyeong)
- HDCP revocation support, refactoring (Ramalingam)
- Remove DRM_AUTH from IOCTLs which also have
Hi Dave & Daniel,
A fix to close a race opportunity between IRQ handler and RCU.
Two fixes that are also stable, disabling FBC on GLK and HSW EDP fastset
correction.
These patches definitely caused conflicts when merged, resolutions should
be all good.
Regards, Joonas
***
Hi Dave & Daniel,
Still rather quiet, most issues seem to have been fixed during CI testing.
For i915, just two fixes to the request semaphore ordering code.
For GVT a couple regression and static checker fixes.
Best Regards,
Joonas
***
drm-intel-next-fixes-2019-05-09:
- Two fixes for the
Hi Dave & Daniel,
A quick fix to unbreak media driver, worthy inclusion before the merge window.
Best Regards,
Joonas
***
drm-intel-next-fixes-2019-05-02:
- Whitelist a register to avoid media driver from hanging
The following changes since commit 879a4e70f96a26a9368a3caed2f552aa67105852:
Hi Dave & Daniel,
Just one fix to fix Icelake CSC programming (fixes loss of blue channel).
Best Regards, Joonas
***
drm-intel-next-fixes-2019-04-30:
- Fix to Icelake CSC losing blue channel
The following changes since commit 447811a686e8da7325516a78069ccfbd139ef1a7:
drm/i915/icl: Fix
Hi Dave & Daniel,
Just one use-after-free fix and Icelake DP programming fix.
Best Regards, Joonas
***
drm-intel-next-fixes-2019-04-25:
- Use after free fix during GEM_CREATE when reporting back object size
- Icelake DP register programming order fix
The following changes since commit
On Thu, Apr 18, 2019 at 11:04:26AM +0300, Joonas Lahtinen wrote:
> - Suppress spurious combo PHY B warning (Vile)
That's putting it a bit strong :)
--
Ville Syrjälä
Intel
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
Hi Dave & Daniel,
A bag of Icelake fixes still. As the biggest thing software frequency
control was found out to be ineffective due to register change.
We've got GEM_BUSY regression fix (noticed by media folks) and
reset handling improvements. For display there's the HDR work and
plenty of
Quoting Dave Airlie (2019-03-28 04:09:56)
> On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen
> wrote:
> >
> > Hi Dave & Daniel,
> >
> > First batch of features for 5.2, tagged last week.
>
> I asked on irc, but got no answer I saw,
>
Hi Dave & Daniel,
Here's a pull request with a further drop of features. Sending this instead of
the build warning fix to avoid diverging the trees. To avoid such build warnings
in futore, I'll talk about doing a non-debug build of the PR tags. The build
warning only occurred when selftests were
On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen
wrote:
>
> Hi Dave & Daniel,
>
> First batch of features for 5.2, tagged last week.
I asked on irc, but got no answer I saw,
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/i915_gem_context.c:698:12:
warning: ‘context_barrier_task’ defined
Hi Dave & Daniel,
First batch of features for 5.2, tagged last week.
Most notably there are a lot of Icelake fixes that finally lead to removal
of alpha_support protection for it. We're also adding Cometlake PCI IDs
(Gen9 ~= Coffeelake), so those platforms should be supported.
Then we have HDCP
Hi Dave and Daniel,
Here goes drm-intel-next-fixes-2019-03-12:
- HDCP state handling in ddi_update_pipe
- Protect i915_active iterators from the shrinker
- Reacquire priolist cache after dropping the engine lock
- (Selftest) Always free spinner on __sseu_prepare error
- Acquire breadcrumb ref
Hi Dave and Daniel,
This is the last batch from us targeting 5.1
Here goes drm-intel-next-2019-02-07:
UAPI Changes:
- Expose RPCS (SSEU) configuration to userspace for Ice Lake
in order to allow userspace to reconfigure the subslice config
per context basis. (Tvrtko, Lionel)
Driver Changes:
-
On Mon, 04 Feb 2019, Daniel Vetter wrote:
> On Mon, Feb 04, 2019 at 10:47:36AM +0200, Joonas Lahtinen wrote:
>> Quoting Dave Airlie (2019-02-04 07:02:07)
>> > On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote:
>> > >
>> > > Hi Dave and Daniel,
>> > >
>> > > Here goes another pull request for 5.1.
On Mon, Feb 04, 2019 at 10:47:36AM +0200, Joonas Lahtinen wrote:
> Quoting Dave Airlie (2019-02-04 07:02:07)
> > On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote:
> > >
> > > Hi Dave and Daniel,
> > >
> > > Here goes another pull request for 5.1.
> >
> > dim complained:
> >
> > Chris committed
Quoting Dave Airlie (2019-02-04 07:02:07)
> On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote:
> >
> > Hi Dave and Daniel,
> >
> > Here goes another pull request for 5.1.
>
> dim complained:
>
> Chris committed this without an S-O-B, now because it's all Intel this
> probably doesn't matter, so
On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote:
>
> Hi Dave and Daniel,
>
> Here goes another pull request for 5.1.
dim complained:
Chris committed this without an S-O-B, now because it's all Intel this
probably doesn't matter, so I'll pull it, put please try and let it
not happen again.
Hi Dave and Daniel,
Here goes another pull request for 5.1.
Maybe I will still send another next week.
This pull also include a GVT one with:
"
Here is gvt-next stuff. This includes Coffeelake support for GVT,
making kvmgt as self load module to have better dependence with
vfio/mdev, with some
Hi Dave,
This pull includes the tag as described below and the GVT stuff, which
"
includes Coffeelake support for GVT,
making kvmgt as self load module to have better dependence with
vfio/mdev, with some const treatment and kernel type change.
"
Also please notice that we have a drm color
Hi Dave and Daniel,
Here goes first pull request targeting 5.1
made out of 2 tags:
drm-intel-next-2019-01-10:
- Unwind failure on pinning the gen7 PPGTT (Chris)
- Fastset updates to make sure DRRS and PSR are properly enabled (Hans)
- Header include clean-up (Brajeswar, Jani)
- Improvements and
Hi Dave & Daniel -
These GVT fixes missed the main pull request.
drm-intel-next-fixes-2018-12-27:
GVT fixes for v4.21-rc1
BR,
Jani.
The following changes since commit e69aa5f9b97f7f871643336deb281db5cb14878b:
Merge tag 'drm-misc-next-2018-12-06' of
Hi Dave, last i915 changes for -next.
drm-intel-next-2018-12-04:
Final drm/i915 changes for v4.21:
- ICL DSI video mode enabling (Madhav, Vandita, Jani, Imre)
- eDP sink count fix (José)
- PSR fixes (José)
- DRM DP helper and i915 DSC enabling (Manasi, Gaurav, Anusha)
- DP FEC enabling (Anusha)
Hi Dave -
This one superseeds and includes everything in [1] as requested, and is
thus pretty big. There are a number of commits that touch non-i915
files, but all relevant acks should be in place. There's also a drm-next
backmerge in there.
BR,
Jani.
[1]
On Fri, 2 Nov 2018 at 20:21, Jani Nikula wrote:
>
>
> Hi Dave -
>
> I just tagged this minutes ago, but I'm sending this now because I'll be
> out for about a week. I don't expect you to pull this until some time
> after -rc1 anyway. I'm asking Joonas and Rodrigo to tell you if this
> one's a go
Hi Dave -
I just tagged this minutes ago, but I'm sending this now because I'll be
out for about a week. I don't expect you to pull this until some time
after -rc1 anyway. I'm asking Joonas and Rodrigo to tell you if this
one's a go or a no go.
There's a couple of backmerges in there, and I'd
Hi Dave,
One fix to avoid applying link retraining workaround on eDP monitors
that was missing Fixes: (kindly pointed out by Jani) in addition
to the patches in previous PR.
I also got GVT PR for -next-fixes, but it had an issue with S-o-bs,
so I'll include it then in -fixes pull.
Regards,
On Fri, Oct 19, 2018 at 12:38 PM Joonas Lahtinen
wrote:
>
> Hi Dave,
>
> Here are the promised MST fixes that were missing due to being
> in i915 tree, yet outside i915 directory.
>
> Further explanation in the previous PR's thread.
fwiw, lgtm.
Cheers, Daniel
>
> Regards, Joonas
>
> ***
>
>
Hi Dave,
Here are the promised MST fixes that were missing due to being
in i915 tree, yet outside i915 directory.
Further explanation in the previous PR's thread.
Regards, Joonas
***
drm-intel-next-fixes-2018-10-19:
- The missing 4 MST patches that tooling didn't pick from drm core/nouveau
Quoting Daniel Vetter (2018-10-19 10:05:32)
> On Fri, Oct 19, 2018 at 8:59 AM Joonas Lahtinen
> wrote:
> >
> > Quoting Daniel Vetter (2018-10-18 22:32:00)
> > > On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen
> > > wrote:
> > > >
> > > > Hi Dave,
> > > >
> > > > Here comes the final set of fixes
On Fri, Oct 19, 2018 at 8:59 AM Joonas Lahtinen
wrote:
>
> Quoting Daniel Vetter (2018-10-18 22:32:00)
> > On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen
> > wrote:
> > >
> > > Hi Dave,
> > >
> > > Here comes the final set of fixes under -next-fixes umbrella.
> > > Next one will be then from
Quoting Daniel Vetter (2018-10-18 22:32:00)
> On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen
> wrote:
> >
> > Hi Dave,
> >
> > Here comes the final set of fixes under -next-fixes umbrella.
> > Next one will be then from -fixes, assuming a release next Sun.
> >
> > Fixes for bunch of display
On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen
wrote:
>
> Hi Dave,
>
> Here comes the final set of fixes under -next-fixes umbrella.
> Next one will be then from -fixes, assuming a release next Sun.
>
> Fixes for bunch of display related issues reported by users, then the
> MST fixes that were
Hi Dave,
Here comes the final set of fixes under -next-fixes umbrella.
Next one will be then from -fixes, assuming a release next Sun.
Fixes for bunch of display related issues reported by users, then the
MST fixes that were dropped from Rodrigos PR + further Icelake fixes
and proactive
Hi Dave,
Here comes -fixes for drm-next.
One compiler warning fix and adding back a removed max stride
check, nothing end user visible.
Regards, Joonas
PS. Travelling next week, so I'll skip PR unless there's
something big.
---
drm-intel-next-fixes-2018-10-04:
Compiler warning fix and
Hi Dave,
Here's the second and final set of changes for v4.20, tagged
last Friday before -rc5. We run it through the testing with
the CI farm machines and found no regressions.
Most user noticeable things are MythTV video stuttering
regression fix for older hardware, black screen fix on resume
Hi Dave,
Here's the first batch of changes for v4.20. Nothing too special.
Notable things are more Icelake enabling/fixing patches and PPGTT
enabling for some older platforms. Icelake is still behind
alpha_support flag as we have the code in upstream but extensive
testing is pending hardware
Hi Dave,
This is the pull request that I tried to send
few days ago, but apparently I had some issue
with my mutt/smtp and it didn't go through.
Well, I don't think that there is anything critical
that cannot wait another week or -rc2
Anyway I'm sending just in case, for the record,
and to try
Hi Dave,
Here goes drm-intel-next-fixes-2018-08-16-1:
Fixes for:
- DP full color range.
- selftest for gem_object
- forcewake on suspend
- GPU reset
This also include accumulated fixes from GVT:
- Fix an error code in gvt_dma_map_page() (Dan)
- Fix off by one error in intel_vgpu_write_fence()
Hi Dave,
Initial fixes for 4.19. Starting by the one where gvt compilation gets
broken after a silent conflict between next and fixes.
Here goes drm-intel-next-fixes-2018-08-06:
- Fix gvt compilation broken on a silent conflict on fixes vs next merge
- Fix runtime PM for LPE audio
- Revert on
Hi Dave,
This is our final pull request for 4.19.
I was waiting some gvt pull that I had nacked for lack of review,
but that didn't came on time and it will have to wait for next-fixes
or later.
Here goes drm-intel-next-2018-07-19:
On GEM side:
- GuC related fixes (Chris, Michal)
- GTT
Hi Dave,
This is probably the last pull request for 4.19 from our side.
Please remind about the gvt-fixes vs gvt-next conflict that I mentioned
yesterday on drm-intel-fixes pull request.
Here goes drm-intel-next-2018-07-12:
On GVT there's the addition of vGPU huge page support for guest,
with
Hi Dave,
This is probably the last big pull targeting 4.19.
I will probably send another small one by the end of this week and
if possible another smaller one by next one.
Here goes drm-intel-next-2018-07-09:
Higlights here goes to many PSR fixes and improvements; to the Ice lake work
with
Hi Dave,
Here goes another pull request for 4.19.
Highlights here to Ice Lake Display enabling, and to preparation for
full-ppgtt enabling for older gens, and to hangcheck and gpu reset
improvements in general.
drm-intel-next-2018-06-20:
Chris is doing many reworks that allow us to get
On Mon, Jun 18, 2018 at 09:12:55AM +0200, Daniel Vetter wrote:
> On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula
> wrote:
> > On Tue, 12 Jun 2018, Dave Airlie wrote:
> >> On 12 June 2018 at 02:27, Rodrigo Vivi wrote:
> >>> Hi Dave,
> >>>
> >>> This is the first round targeting 4.19.
> >>>
> >>
On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula
wrote:
> On Tue, 12 Jun 2018, Dave Airlie wrote:
>> On 12 June 2018 at 02:27, Rodrigo Vivi wrote:
>>> Hi Dave,
>>>
>>> This is the first round targeting 4.19.
>>>
>> Does this tree feed into linux-next already?
>>
>> Since we shouldn't have new stuff
On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula
wrote:
> On Tue, 12 Jun 2018, Dave Airlie wrote:
>> On 12 June 2018 at 02:27, Rodrigo Vivi wrote:
>>> Hi Dave,
>>>
>>> This is the first round targeting 4.19.
>>>
>> Does this tree feed into linux-next already?
>>
>> Since we shouldn't have new stuff
On Tue, 12 Jun 2018, Dave Airlie wrote:
> On 12 June 2018 at 02:27, Rodrigo Vivi wrote:
>> Hi Dave,
>>
>> This is the first round targeting 4.19.
>>
> Does this tree feed into linux-next already?
>
> Since we shouldn't have new stuff for linux-next feeding into it until
> after rc1.
I think
On 12 June 2018 at 02:27, Rodrigo Vivi wrote:
> Hi Dave,
>
> This is the first round targeting 4.19.
>
Does this tree feed into linux-next already?
Since we shouldn't have new stuff for linux-next feeding into it until
after rc1.
I won't be pulling this until after rc1 anyways.
Dave.
Hi Dave,
This is the first round targeting 4.19.
Here goes drm-intel-next-2018-06-06:
- Ice Lake's display enabling patches (Jose, Mahesh, Dhinakaran, Paulo, Manasi,
Anusha, Arkadiusz)
- Ice Lake's workarounds (Oscar and Yunwei)
- Ice Lake interrupt registers fixes (Oscar)
- Context switch
101 - 200 of 410 matches
Mail list logo
