On 2021.05.12 09:47:39 -0300, Jason Gunthorpe wrote:
> On Wed, May 12, 2021 at 10:31:41AM +0800, Zhenyu Wang wrote:
>
> > > This need to go into the vfio tree in some way, either directly
> > > through it, via rc or otherwise
> >
> > As this is only for i915/gvt, once drm/i915 backmerge with linu
== Series Details ==
Series: drm/dp_mst: Use kHz as link rate units when settig source max link caps
at init
URL : https://patchwork.freedesktop.org/series/90099/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20114_full
== Series Details ==
Series: drm/i915: Check HDMI sink deep color capabilities during .mode_valid()
(rev2)
URL : https://patchwork.freedesktop.org/series/90036/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20113_full
==
== Series Details ==
Series: CI pass for reviewed XeLPD / ADL-P patches (rev3)
URL : https://patchwork.freedesktop.org/series/90048/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20112_full
Summary
-
Ville,
DPCD DFP: 0a
What is the DPCD DFP?
Additional info, this is the first time there has been an issue with this
adapter not working (i.e. it must have been operating above 165MHz), but it is
possible other drivers have "ignored" things and just followed the EDID.
Thanks!
Adam
kernel: [drm
Reviewed-by: Dave Airlie
Can we get this fix in, having a regression spanning 3 kernels isn't a
good look, we can work out why it matters later in life if anyone
cares.
Dave.
On Tue, 27 Apr 2021 at 00:31, Simon Rettberg
wrote:
>
> When resetting CACHE_MODE registers, don't enable HiZ Raw Stall
On Wed, May 12, 2021 at 09:47:26PM +, Patchwork wrote:
> == Series Details ==
>
> Series: CI pass for reviewed XeLPD / ADL-P patches (rev2)
> URL : https://patchwork.freedesktop.org/series/90048/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10071_full -> Patchwo
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 36/48] drm/i915/adl_p: Enable/disable loadgen
> sharing
>
> From: Mika Kahola
>
> Disable loadgen sharing for DP
Hi Lakshmi,
On Wed, May 12, 2021 at 10:23:59PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4
> URL : https://patchwork.freedesktop.org/series/90102/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Nikula, Jani
> Subject: [Intel-gfx] [PATCH v3 44/48] drm/i915/adl_p: Add IPs stepping
> mapping
>
> From: José Roberto de Souza
>
> This wi
On Fri, May 07, 2021 at 07:52:43PM -0700, Matt Roper wrote:
From: Vandita Kulkarni
Add the qp table for 444 formats, for 8bpc, 10bpc and 12bpc, as given by
the VESA C model for DSC 1.1
v2:
- Add include guard to header (Jani)
- Move the big tables to a .c file (Chris, Jani, Lucas)
v3:
- Make t
== Series Details ==
Series: drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4
URL : https://patchwork.freedesktop.org/series/90102/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20115
Sum
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 39/48] drm/i915/bigjoiner: Mode validation
> with uncompressed pipe joiner
>
> From: Animesh Manna
>
> No need f
== Series Details ==
Series: CI pass for reviewed XeLPD / ADL-P patches (rev2)
URL : https://patchwork.freedesktop.org/series/90048/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10071_full -> Patchwork_20107_full
Summary
-
== Series Details ==
Series: drm/dp_mst: Use kHz as link rate units when settig source max link caps
at init
URL : https://patchwork.freedesktop.org/series/90099/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20114
==
On Fri, May 07, 2021 at 07:27:33PM -0700, Matt Roper wrote:
XE_LPD has new AUX interrupt bits for DDI-D and DDI-E that take the
spots that were used by TC5/TC6 on Display12 platforms.
While we're at it, let's convert the bit definitions for all TGL+ aux
bits over to the modern REG_BIT() notation
The driver currently disables the LTTPR non-transparent link training
mode for sinks with a DPCD_REV<1.4, based on the following description
of the LTTPR DPCD register range in DP standard 2.0 (at the 0xF
register description):
""
LTTPR-related registers at DPCD Addresses Fh through F02FFh
== Series Details ==
Series: drm/dp_mst: Use kHz as link rate units when settig source max link caps
at init
URL : https://patchwork.freedesktop.org/series/90099/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c9bc0648dd46 drm/dp_mst: Use kHz as link rate units when settig sour
[why]
Link rate in kHz is what is eventually required to calculate the link
bandwidth, which makes kHz a more generic unit. This should also make
forward-compatibility with new DP standards easier.
[how]
- Replace 'link rate DPCD code' with 'link rate in kHz' when used with
drm_dp_mst_topology_mgr
Change log:
v2:
- Added 'Acked-by' to comment
v1:
- Initial
Nikola Cornij (1):
drm/dp_mst: Use kHz as link rate units when settig source max link
caps at init
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 4 ++--
drivers/gpu/drm/drm_dp_mst_topology.c
== Series Details ==
Series: drm/i915: Check HDMI sink deep color capabilities during .mode_valid()
(rev2)
URL : https://patchwork.freedesktop.org/series/90036/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20113
Hoping I can (help) craft a patch to address what appears to be an issue with
overaggressive mode pruning. I am having trouble with rejection of a Dual-DVI
compatible mode out of the DisplayPort specific to i915 in Fedora 33. It seems
that drm_mode_validate_pipeline is the wall I hit when diggi
== Series Details ==
Series: CI pass for reviewed XeLPD / ADL-P patches (rev3)
URL : https://patchwork.freedesktop.org/series/90048/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20112
Summary
---
On Wed, May 12, 2021 at 12:31:14PM -0400, Adam Chasen wrote:
> Hoping I can (help) craft a patch to address what appears to be an issue with
> overaggressive mode pruning. I am having trouble with rejection of a Dual-DVI
> compatible mode out of the DisplayPort specific to i915 in Fedora 33. It
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 35/48] drm/i915/adl_p: Define and use ADL-P
> specific DP translation tables
>
> From: Mika Kahola
>
> Define an
== Series Details ==
Series: CI pass for reviewed XeLPD / ADL-P patches (rev3)
URL : https://patchwork.freedesktop.org/series/90048/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+drivers/gpu/drm
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 15/48] drm/i915/xelpd: Provide port/phy
> mapping for vbt
>
> From: José Roberto de Souza
>
> This will allow pro
On Tue, 04 May 2021, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> For some reason the dg1 buf trans tables have been stuffed into
> icl_get_combo_buf_trans_edp() which doesn't even get called
> on dg1. Split them out into a proper dg1 specific function,
> and also make sure we use the proper bu
On Wed, 21 Apr 2021, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Give RKL its own get_buf_trans() func.
>
> Note that the spec currently only lists values for DP.
> Until we get that clarified let's just assume that for
> HDMI and eDP we should do what TGL does (except we fall
> back to the RK
Hi
Am 12.05.21 um 07:00 schrieb Stephen Rothwell:
Hi all,
After merging the drm-misc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpu/drm/nouveau/nouveau_connector.c: In function
'nouveau_connector_of_detect':
drivers/gpu/drm/nouveau/nouveau_connector.c:463:
On Wed, 21 Apr 2021, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Split the hsw/bdw/skl/kbl get_buf_trans() functions into
> clean platform specific variants.
One of the most obnoxious patches to review lately, but it was worth it.
Reviewed-by: Jani Nikula
>
> Signed-off-by: Ville Syrjälä
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 09/48] drm/i915/display/dsc: Refactor
> intel_dp_dsc_compute_bpp
>
> From: Vandita Kulkarni
>
> Move the platfor
On Wed, May 12, 2021 at 9:04 AM Ville Syrjälä
wrote:
>
> On Wed, May 12, 2021 at 02:06:56PM +0200, Werner Sembach wrote:
> > Hello,
> >
> > In addition to the existing "max bpc", and "Broadcast RGB/output_csc" drm
> > properties I propose 4 new properties:
> > "preferred pixel encoding", "active
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 06/48] drm/i915/xelpd: Increase maximum
> watermark lines to 255
>
> XE_LPD continues to use the same "skylake-styl
Re-reported.
-Original Message-
From: Roper, Matthew D
Sent: Wednesday, May 12, 2021 9:18 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for CI pass for reviewed XeLPD / ADL-P
patches (rev2)
On Wed, May 12, 2021 at 06:13:10AM +,
== Series Details ==
Series: CI pass for reviewed XeLPD / ADL-P patches (rev2)
URL : https://patchwork.freedesktop.org/series/90048/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10071 -> Patchwork_20107
Summary
---
== Series Details ==
Series: CI pass for reviewed XeLPD / ADL-P patches (rev2)
URL : https://patchwork.freedesktop.org/series/90048/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10071 -> Patchwork_20107
Summary
---
On Wed, 2021-05-12 at 17:17 +0200, Mauro Carvalho Chehab wrote:
> Em Wed, 12 May 2021 10:14:44 -0400
> "Theodore Ts'o" escreveu:
>
> > On Wed, May 12, 2021 at 02:50:04PM +0200, Mauro Carvalho Chehab wrote:
> > > v2:
> > > - removed EM/EN DASH conversion from this patchset;
> >
> > Are you stil
Your title 'Use ASCII subset' is now at least a bit *closer* to
describing what the patches are actually doing, but it's still a bit
misleading because you're only doing it for *some* characters.
And the wording is still indicative of a fundamentally *misguided*
motivation for doing any of this. Y
> -Original Message-
> From: Intel-gfx On Behalf Of Matt
> Roper
> Sent: Friday, May 7, 2021 7:28 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 28/48] drm/i915: Move
> intel_modeset_all_pipes()
>
> From: Ville Syrjälä
>
> Move intel_modeset_all_pipes() to a
Matt, Gitlab is down at the moment. We have a similar bug but I need to still
confirm the same. Once the gitlab is up and running I will check and if
required I will a new issue and re-report the results.
I will re-visit gitlab issues later today.
Lakshmi.
-Original Message-
From: Rop
> -Original Message-
> From: Jani Nikula
> Sent: Wednesday, May 12, 2021 6:38 AM
> To: Srivatsa, Anusha ; intel-
> g...@lists.freedesktop.org
> Cc: Srivatsa, Anusha
> Subject: Re: [PATCH 5/5] drm/i915/dmc: s/intel_csr.c/intel_dmc.c and
> s/intel_csr.h/intel_dmc.h
>
> On Tue, 11 May 202
On Wed, May 12, 2021 at 06:13:10AM +, Patchwork wrote:
> == Series Details ==
>
> Series: CI pass for reviewed XeLPD / ADL-P patches (rev2)
> URL : https://patchwork.freedesktop.org/series/90048/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10071 -> Patchwork_20
Em Wed, 12 May 2021 10:14:44 -0400
"Theodore Ts'o" escreveu:
> On Wed, May 12, 2021 at 02:50:04PM +0200, Mauro Carvalho Chehab wrote:
> > v2:
> > - removed EM/EN DASH conversion from this patchset;
>
> Are you still thinking about doing the
>
> EN DASH --> "--"
> EM DASH --> "---"
>
> conver
The conversion tools used during DocBook/LaTeX/Markdown->ReST conversion
and some automatic rules which exists on certain text editors like
LibreOffice turned ASCII characters into some UTF-8 alternatives that
are better displayed on html and PDF.
While it is OK to use UTF-8 characters in Linux, i
This series contain basically a cleanup from all those years of converting
files to ReST.
During the conversion period, several tools like LaTeX, pandoc, DocBook
and some specially-written scripts were used in order to convert
existing documents.
Such conversion tools - plus some text editor like
Am 12.05.21 um 14:06 schrieb Werner Sembach:
> Hello,
>
> In addition to the existing "max bpc", and "Broadcast RGB/output_csc" drm
> properties I propose 4 new properties:
> "preferred pixel encoding", "active color depth", "active color range", and
> "active pixel encoding"
>
>
> Motivation:
>
== Series Details ==
Series: drm/i915: split out new intel_backlight.[ch]
URL : https://patchwork.freedesktop.org/series/90078/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20111
Summary
---
**FAI
Hi Dave and Daniel,
here's the first PR for drm-misc-next for what will go into v5.14. Some
noteable changes are
* consistency between the plane formats and allow_fb_modifiers in UAPI,
* overlay support in vkms,
* proper HDR support in vc4,
* SVGA3 support in vmwgfx,
* many TTM fixes and a d
On Wed, May 12, 2021 at 02:50:04PM +0200, Mauro Carvalho Chehab wrote:
> v2:
> - removed EM/EN DASH conversion from this patchset;
Are you still thinking about doing the
EN DASH --> "--"
EM DASH --> "---"
conversion? That's not going to change what the documentation will
look like in the HTML a
== Series Details ==
Series: drm/i915: split out new intel_backlight.[ch]
URL : https://patchwork.freedesktop.org/series/90078/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5c56f5e2aca2 drm/i915/backlight: extract backlight code to a separate file
-:57: WARNING:FILE_PATH_CHANG
On Tue, 11 May 2021, Anusha Srivatsa wrote:
> Currently in our driver we use both CSR and DMC interchangeably.
> Even though the spec mentions both, we do not follow that convention
> in the driver.
>
> Renaming all references of CSR to just be DMC. This hopefully makes
> the driver of this part a
On Tue, 11 May 2021, Anusha Srivatsa wrote:
> Finally, rename the header and source file from csr to dmc.
>
> Cc: Jani Nikula
> Signed-off-by: Anusha Srivatsa
> ---
> drivers/gpu/drm/i915/Makefile | 2 +-
> drivers/gpu/drm/i915/display/intel_display.c |
Follow the usual naming conventions. Also pull HAS_GMCH() check to
intel_panel_fitting(). No functional changes.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/icl_dsi.c | 4 ++--
drivers/gpu/drm/i915/display/intel_dp.c| 9 +++-
drivers/gpu/drm/i915/display/intel_dvo.c
Follow the usual naming conventions. As a drive-by cleanup, also pass
intel_connector instead of drm_connector to intel_backlight_setup(). No
functional changes.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/g4x_dp.c | 2 +-
drivers/gpu/drm/i915/display/icl_dsi.c|
Long overdue refactoring.
This should not conflict with Lyude's dpcd backlight refactoring [1],
but if it does, that series should have precedence.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/84754/
Jani Nikula (3):
drm/i915/backlight: extract backlight code to a separate file
d
On 5/12/21 3:05 PM, Christian König wrote:
Am 12.05.21 um 15:02 schrieb Thomas Hellström:
On Wed, 2021-05-12 at 09:09 +0200, Christian König wrote:
Am 12.05.21 um 09:05 schrieb Thomas Hellström:
On Wed, 2021-05-12 at 08:57 +0200, Christian König wrote:
Am 11.05.21 um 16:28 schrieb Thomas Hel
== Series Details ==
Series: drm/i915/gem: Pin the L-shape quirked object as unshrinkable
URL : https://patchwork.freedesktop.org/series/90065/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10073 -> Patchwork_20110
Summary
On Wednesday, May 12th, 2021 at 3:04 PM, Ville Syrjälä
wrote:
> > Adoption:
> >
> > A KDE dev wants to implement the settings in the KDE settings GUI:
> >
> > https://gitlab.freedesktop.org/drm/amd/-/issues/476#note_912370
> >
> > Tuxedo Computers (my employer) wants to implement the settings de
Am 12.05.21 um 15:02 schrieb Thomas Hellström:
On Wed, 2021-05-12 at 09:09 +0200, Christian König wrote:
Am 12.05.21 um 09:05 schrieb Thomas Hellström:
On Wed, 2021-05-12 at 08:57 +0200, Christian König wrote:
Am 11.05.21 um 16:28 schrieb Thomas Hellström:
On 5/11/21 4:09 PM, Christian König
On Wed, May 12, 2021 at 02:06:56PM +0200, Werner Sembach wrote:
> Hello,
>
> In addition to the existing "max bpc", and "Broadcast RGB/output_csc" drm
> properties I propose 4 new properties:
> "preferred pixel encoding", "active color depth", "active color range", and
> "active pixel encoding"
On Wed, 2021-05-12 at 09:09 +0200, Christian König wrote:
> Am 12.05.21 um 09:05 schrieb Thomas Hellström:
> > On Wed, 2021-05-12 at 08:57 +0200, Christian König wrote:
> > > Am 11.05.21 um 16:28 schrieb Thomas Hellström:
> > > > On 5/11/21 4:09 PM, Christian König wrote:
> > > > >
> > > > > Am 11
== Series Details ==
Series: Revert hardcoded lockdep values.
URL : https://patchwork.freedesktop.org/series/90059/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10073 -> Patchwork_20108
Summary
---
**FAILURE**
Se
== Series Details ==
Series: i915 clear-residuals BYT + IVB rendering issue + possible fix
URL : https://patchwork.freedesktop.org/series/90062/
State : failure
== Summary ==
Applying: i915 clear-residuals BYT + IVB rendering issue + possible fix
error: patch failed: drivers/gpu/drm/i915/gt/ge
Hi,
On 5/12/21 1:57 PM, Christoph Hellwig wrote:
> On Wed, May 12, 2021 at 01:15:03PM +0200, Peter Zijlstra wrote:
>> IIRC it's because of 74ffa5a3e685 ("mm: add remap_pfn_range_notrack"),
>> which added a sanity check to make sure expectations were met. It turns
>> out they were not.
>>
>> The bu
Hi,
On 5/12/21 2:18 PM, Ville Syrjälä wrote:
> On Wed, May 12, 2021 at 12:06:23PM +0200, Hans de Goede wrote:
>> Hi All,
>>
>> We (Fedora) received a bug-report about rendering issues
>> on BYT and IVB caused by the i915 clear-residuals work
>> which landed in 5.10.y :
>>
>> The Fedora bug:
>> htt
On Wed, May 12, 2021 at 12:06:23PM +0200, Hans de Goede wrote:
> Hi All,
>
> We (Fedora) received a bug-report about rendering issues
> on BYT and IVB caused by the i915 clear-residuals work
> which landed in 5.10.y :
>
> The Fedora bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1959581
>
>
== Series Details ==
Series: Revert hardcoded lockdep values.
URL : https://patchwork.freedesktop.org/series/90059/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3e74c76de424 Revert hardcoded lockdep values.
-:43: WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email addre
Hello,
In addition to the existing "max bpc", and "Broadcast RGB/output_csc" drm
properties I propose 4 new properties:
"preferred pixel encoding", "active color depth", "active color range", and
"active pixel encoding"
Motivation:
Current monitors have a variety pixel encodings available: RG
On Wed, May 12, 2021 at 01:15:03PM +0200, Peter Zijlstra wrote:
> IIRC it's because of 74ffa5a3e685 ("mm: add remap_pfn_range_notrack"),
> which added a sanity check to make sure expectations were met. It turns
> out they were not.
>
> The bug is not new, the warning is. AFAIK the i915 team is awa
Hi, Matthew,
Thanks for reviewing!
On 5/12/21 1:45 PM, Matthew Auld wrote:
On Tue, 11 May 2021 at 14:26, Thomas Hellström
wrote:
Most logical place to introduce TTM buffer objects is as an i915
gem object backend. We need to add some ops to account for added
functionality like delayed delete
On Tue, 11 May 2021 at 14:26, Thomas Hellström
wrote:
>
> Most logical place to introduce TTM buffer objects is as an i915
> gem object backend. We need to add some ops to account for added
> functionality like delayed delete and LRU list manipulation.
>
> Initially we support only LMEM and SYSTEM
On Wed, May 12, 2021 at 11:57:02AM +0200, Hans de Goede wrote:
> Hi All,
>
> I'm not sure if this is a i915 bug, or caused by changes elsewhere in the
> kernel,
> so I thought it would be best to just send out an email and then see from
> there.
>
> With 5.13-rc1 gdm fails to show and dmesg con
From: Chris Wilson
When instantiating a tiled object on an L-shaped memory machine, we mark
the object as unshrinkable to prevent the shrinker from trying to swap
out the pages. We have to do this as we do not know the swizzling on the
individual pages, and so the data will be scrambled across sw
Hi All,
We (Fedora) received a bug-report about rendering issues
on BYT and IVB caused by the i915 clear-residuals work
which landed in 5.10.y :
The Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1959581
Points to these i915 bugs:
https://gitlab.freedesktop.org/drm/intel/-/issues/3071
h
Hi All,
I'm not sure if this is a i915 bug, or caused by changes elsewhere in the
kernel,
so I thought it would be best to just send out an email and then see from there.
With 5.13-rc1 gdm fails to show and dmesg contains:
[ 38.504613] x86/PAT: Xwayland:683 map pfn RAM range req write-combini
For CI testing, config should be updated now.
Revert "lockdep: Bump MAX_STACK_TRACE_ENTRIES"
This reverts commit 8733308e6c3929b28fdf4bda6b4629f094f6547d.
Revert "lockdep: Up MAX_LOCKDEP_CHAINS"
This reverts commit 39eca5b925699687a7d638a866f74e79f48f73a9.
Once CI approves we can drop the above t
On Thu, May 06, 2021 at 03:23:43PM +0200, Daniel Vetter wrote:
> It's very confusing for userspace to have to deal with inconsistencies
> here, and some drivers screwed this up a bit. Most just ommitted the
> format list when they meant to say that only linear modifier is
> allowed, but some also m
On Tue, 11 May 2021 at 14:26, Thomas Hellström
wrote:
>
> Temporarily remove the buddy allocator and related selftests
> and hook up the TTM range manager for i915 regions.
>
> In order to support some of the mock region-related selftests, we need to
> be able to initialize the TTM range-manager s
On Wed, May 12, 2021 at 12:11:40AM +0200, Michal Wajdeczko wrote:
>
>
> On 11.05.2021 17:16, Daniel Vetter wrote:
> > On Thu, May 06, 2021 at 12:13:34PM -0700, Matthew Brost wrote:
> >> From: Michal Wajdeczko
> >>
> >> New GuC firmware will unify format of MMIO and CTB H2G messages.
> >> Introdu
On Tue, May 11, 2021 at 11:44:28AM -0700, Matthew Brost wrote:
> On Tue, May 11, 2021 at 05:11:44PM +0200, Daniel Vetter wrote:
> > On Thu, May 06, 2021 at 10:30:48AM -0700, Matthew Brost wrote:
> > > i915_drm.h updates for 'set parallel submit' extension.
> > >
> > > Cc: Tvrtko Ursulin
> > > Cc:
On Wed, May 12, 2021 at 08:38:55AM +0100, Matthew Auld wrote:
> On 11/05/2021 18:29, Daniel Vetter wrote:
> > On Tue, May 11, 2021 at 07:28:08PM +0200, Daniel Vetter wrote:
> > > On Tue, May 11, 2021 at 06:03:56PM +0100, Matthew Auld wrote:
> > > > The proper headers have now landed in include/uapi
On Tue, 11 May 2021 at 14:26, Thomas Hellström
wrote:
>
> Since objects can be migrated or evicted when not pinned or locked,
> update the checks for lmem residency or future residency so that
> the value returned is not immediately stale.
>
> Signed-off-by: Thomas Hellström
> ---
> drivers/gpu/
On 11/05/2021 18:29, Daniel Vetter wrote:
On Tue, May 11, 2021 at 07:28:08PM +0200, Daniel Vetter wrote:
On Tue, May 11, 2021 at 06:03:56PM +0100, Matthew Auld wrote:
The proper headers have now landed in include/uapi/drm/i915_drm.h, so we
can drop i915_gem_lmem.h and instead just reference the
Pushed to drm-intel-next there was unrelated CI failures, instead rev2 was
green https://patchwork.freedesktop.org/series/89639/#rev2
Rev3 was just a rebased.
Thanks for the parch.
Br,
Anshuman Gupta.
From: Intel-gfx On Behalf Of Patchwork
Sent: Tuesday, May 11, 2021 9:49 PM
To: Nautiyal, Ankit
Am 12.05.21 um 09:05 schrieb Thomas Hellström:
On Wed, 2021-05-12 at 08:57 +0200, Christian König wrote:
Am 11.05.21 um 16:28 schrieb Thomas Hellström:
On 5/11/21 4:09 PM, Christian König wrote:
Am 11.05.21 um 16:06 schrieb Thomas Hellström (Intel):
On 5/11/21 3:58 PM, Christian König wrote:
On Wed, 2021-05-12 at 08:57 +0200, Christian König wrote:
> Am 11.05.21 um 16:28 schrieb Thomas Hellström:
> >
> > On 5/11/21 4:09 PM, Christian König wrote:
> > >
> > >
> > > Am 11.05.21 um 16:06 schrieb Thomas Hellström (Intel):
> > > >
> > > > On 5/11/21 3:58 PM, Christian König wrote:
> > >
87 matches
Mail list logo
