Am 11.02.21 um 18:22 schrieb Daniel Vetter:
On Thu, Feb 11, 2021 at 4:27 PM Christian König
wrote:
Am 11.02.21 um 16:02 schrieb Jani Nikula:
On Thu, 11 Feb 2021, Christian König wrote:
Hi guys,
I had a conflict this morning in the ttm pool while pushing an important
fix to
On 2/11/2021 9:32 PM, Jordan Crouse wrote:
On Thu, Feb 11, 2021 at 06:50:28PM +0530, Akhil P Oommen wrote:
On 2/10/2021 6:22 AM, Jordan Crouse wrote:
Most a6xx targets have security issues that were fixed with new versions
of the microcode(s). Make sure that we are booting with a safe version
Hi
Am 11.02.21 um 18:51 schrieb Christopher Morgan:
I'd like to make the following changes to this panel driver. The first patch
is to add rotation support (rotates only the DRM connector at this time). The
panel is currently rotated 270 degrees in the Odroid Go Advance, and this
change
Hi
thanks for the driver. I only have some minor comments
Am 11.02.21 um 10:50 schrieb Daniel Mack:
This patch adds support for Newhaven's NHD-1.8-128160EF display, featuring
an Ilitek ILI9163 controller.
Signed-off-by: Daniel Mack
---
.../bindings/display/ilitek,ili9163.txt | 27
We use mmu_notifier_put to free the MMU notifier. That needs to be
paired with mmu_notifier_get to work correctly. Othewrise the next patch
would cause a kernel oops.
Signed-off-by: Felix Kuehling
---
drivers/gpu/drm/amd/amdkfd/kfd_process.c | 33 +++-
1 file changed, 27
If init_cwsr_apu fails, we currently leave the kfd_process structure in
place anyway. The next kfd_open will then succeed, using the existing
kfd_process structure. Fix that by cleaning up the kfd_process after a
failure in init_cwsr_apu.
Signed-off-by: Felix Kuehling
---
On Thu, Feb 11, 2021 at 11:44 AM Simon Ser wrote:
> On Wednesday, February 10th, 2021 at 11:02 PM, Mario Kleiner <
> mario.kleiner...@gmail.com> wrote:
>
> > I'll prepare patches with the same fix for libdrm and igt as well soon.
>
> Please don't submit patches for drm_fourcc.h to downstream if
(resent with a subject this time)
Hi Linus,
Regular fixes for final, there is a ttm regression fix, dp-mst fix,
one amdgpu revert, two i915 fixes, and some misc fixes for sun4i,
xlnx, and vc4.
All pretty quiet and don't think we have any known outstanding regressions.
Dave.
Hi Linus,
Regular fixes for final, there is a ttm regression fix, dp-mst fix,
one amdgpu revert, two i915 fixes, and some misc fixes for sun4i,
xlnx, and vc4.
All pretty quiet and don't think we have any known outstanding regressions.
Dave.
drm-fixes-2021-02-12:
drm fixes for 5.11-rc8
ttm:
-
Quoting Jernej Skrabec (2021-02-09 09:58:56)
> CLK_SET_RATE_PARENT flag is checked on parent clock instead of current
> one. Fix that.
>
> Fixes: 3f790433c3cb ("clk: sunxi-ng: Adjust MP clock parent rate when
> allowed")
> Reviewed-by: Chen-Yu Tsai
> Tested-by: Andre Heider
> Signed-off-by:
(JFYI I have seen this email, but haven't gotten a chance to actually read
through it yet. I should have the time to do so tomorrow)
On Thu, 2021-02-11 at 06:56 +, Almahallawy, Khaled wrote:
> On Wed, 2021-02-10 at 13:03 -0500, Lyude Paul wrote:
> > On Wed, 2021-02-10 at 00:33 -0800, Khaled
On Wed, Feb 10, 2021 at 10:23:58PM -0500, Rodrigo Vivi wrote:
> On Tue, Feb 09, 2021 at 04:28:31PM -0500, Lyude Paul wrote:
> > Apparently the new gen9_bc platforms that Intel has introduced don't
> > provide us with a STRAP config register to read from for initializing DDI
> > B, C, and D
https://bugzilla.kernel.org/show_bug.cgi?id=211717
Bug ID: 211717
Summary: WARNING: CPU: 5 PID: 430 at
drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn21
/rn_clk_mgr.c:833 rn_clk_mgr_construct+0x2dd/0x440
We don't need to make up custom lock classes here, we can simply use
mutex_lock_nested() and pass in the index of the crtc to the locking
APIs instead. This helps lockdep understand that these are really
different locks while avoiding having to allocate custom lockdep
classes.
Cc: Krishna
On Mon 2021-02-08 22:09:02, Sakari Ailus wrote:
> Now that we can print FourCC codes directly using printk, make use of the
> feature in V4L2 core.
>
> Signed-off-by: Sakari Ailus
> ---
> drivers/media/v4l2-core/v4l2-ioctl.c | 85 +++-
> 1 file changed, 21 insertions(+),
On Tue 2021-02-09 19:47:55, Sakari Ailus wrote:
> Hi Andy,
>
> On Tue, Feb 09, 2021 at 11:58:40AM +0200, Andy Shevchenko wrote:
> > On Tue, Feb 09, 2021 at 11:20:32AM +0200, Sakari Ailus wrote:
> > > On Mon, Feb 08, 2021 at 10:43:30PM +0200, Andy Shevchenko wrote:
> > > > On Mon, Feb 8, 2021 at
The 2021 X.Org Foundation elections are rapidly approaching. In
preparation of the elections we would like to remind you that members
will need to renew their membership each year in order to vote. Please
take the time to renew your membership by logging into
https://members.x.org and clicking
I'd like to make the following changes to this panel driver. The first patch
is to add rotation support (rotates only the DRM connector at this time). The
panel is currently rotated 270 degrees in the Odroid Go Advance, and this
change allows us to describe that hardware better.
The second
Looks like a recent regression?
Begin forwarded message:
Date: Thu, 11 Feb 2021 14:27:43 +
From: bugzilla-dae...@bugzilla.kernel.org
To: a...@linux-foundation.org
Subject: [Bug 211707] New: BUG: unable to handle page fault for address:
a147bdf6b91d
https://bugzilla.kernel.org/show_bug.cgi?id=206987
--- Comment #41 from Jan Kokemüller (jan.kokemuel...@gmail.com) ---
> Looks correct. Care to send out a proper git patch?
Thank you for having a look at the patch! I've sent it to the amd-gfx list.
--
You may reply to this email to add a
On Wed, 2021-02-10 at 23:15 -0500, Rodrigo Vivi wrote:
> On Mon, Feb 08, 2021 at 06:39:00PM -0500, Lyude Paul wrote:
> > Since we're about to implement eDP backlight support in nouveau using the
> > standard protocol from VESA, we might as well just take the code that's
> > already written for
On 2/11/21 3:26 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210210:
>
> The powerpc tree still had its build failure in the allyesconfig for
> which I applied a supplied patch.
>
> The v4l-dvb tree lost its build failure.
>
> The drm-misc tree lost its build failure.
>
> The
The driver already has support for sm8150/sm8250, but the compatibles were
never added.
Also inverse the non-mdp4 condition in add_display_components() to avoid
having to check every new compatible in the condition.
Signed-off-by: Jonathan Marek
---
Add sm8150/sm8250 compatibles to drm/msm and fix the sm8250
display nodes.
Jonathan Marek (2):
drm/msm: add compatibles for sm8150/sm8250 display
arm64: dts: qcom: sm8250: fix display nodes
.../devicetree/bindings/display/msm/dpu.txt | 4 +--
arch/arm64/boot/dts/qcom/sm8250.dtsi
* Tomi Valkeinen [210211 07:35]:
> On 08/02/2021 19:55, Tony Lindgren wrote:
> > Hi,
> >
> > * Tomi Valkeinen [201124 12:47]:
> >> From: Sebastian Reichel
> >>
> >> In preparation for removing custom DSS calls from the DSI
> >> panel driver, this moves support for external tearing event
> >>
On Thu, Feb 11, 2021 at 4:27 PM Christian König
wrote:
>
>
>
> Am 11.02.21 um 16:02 schrieb Jani Nikula:
> > On Thu, 11 Feb 2021, Christian König wrote:
> >> Hi guys,
> >>
> >> I had a conflict this morning in the ttm pool while pushing an important
> >> fix to drm-misc-fixes.
> >>
> >> I'm not
On Thu, Feb 11, 2021 at 04:14:02PM +, Daniel Stone wrote:
> On Wed, 10 Feb 2021 at 15:07, Ville Syrjälä
> wrote:
> > On Wed, Feb 10, 2021 at 01:38:45PM +, Simon Ser wrote:
> > > The WARN_ON only happens if allow_modeset == false. If allow_modeset ==
> > > true,
> > > then the driver is
On Wed, 10 Feb 2021 at 15:07, Ville Syrjälä
wrote:
> On Wed, Feb 10, 2021 at 01:38:45PM +, Simon Ser wrote:
> > The WARN_ON only happens if allow_modeset == false. If allow_modeset ==
> > true,
> > then the driver is allowed to steal an unrelated pipe.
> >
> > Maybe i915 is stealing a pipe
Am 11.02.21 um 16:58 schrieb Daniel Vetter:
On Wed, Feb 10, 2021 at 09:23:52PM +0100, Christian König wrote:
Am 10.02.21 um 19:15 schrieb Daniel Vetter:
On Wed, Feb 10, 2021 at 5:05 PM Christian König
wrote:
The old implementation wasn't consistend on this.
But it looks like we depend on
On Thu, Feb 11, 2021 at 06:50:28PM +0530, Akhil P Oommen wrote:
> On 2/10/2021 6:22 AM, Jordan Crouse wrote:
> >Most a6xx targets have security issues that were fixed with new versions
> >of the microcode(s). Make sure that we are booting with a safe version of
> >the microcode for the target and
On Thu, Feb 11, 2021 at 10:50:58AM +0100, Daniel Mack wrote:
> This patch adds support for Newhaven's NHD-1.8-128160EF display, featuring
> an Ilitek ILI9163 controller.
>
> Signed-off-by: Daniel Mack
> ---
> .../bindings/display/ilitek,ili9163.txt | 27 +++
I think the dt stuff needs to
On Wed, Feb 10, 2021 at 09:23:52PM +0100, Christian König wrote:
>
>
> Am 10.02.21 um 19:15 schrieb Daniel Vetter:
> > On Wed, Feb 10, 2021 at 5:05 PM Christian König
> > wrote:
> > > The old implementation wasn't consistend on this.
> > >
> > > But it looks like we depend on this so better
On Wed, Feb 10, 2021 at 03:26:00PM -0800, Navare, Manasi wrote:
> On Wed, Feb 10, 2021 at 05:07:03PM +0200, Ville Syrjälä wrote:
> > On Wed, Feb 10, 2021 at 01:38:45PM +, Simon Ser wrote:
> > > On Wednesday, February 10th, 2021 at 2:16 PM, Daniel Vetter
> > > wrote:
> > >
> > > > On Tue,
hi Dave,
Here a pull request for drm-misc-next-fixes, I'm not 100% sure about all the
CEC fixes,
but seems like it wouldn't hurt. We could revert the flag that enables CEC if
needed.
I just picked everything that looked like fixes from drm-misc-next.
drm-misc-next-fixes-2021-02-11:
On Wed, Feb 10, 2021 at 04:12:58PM +, Lee Jones wrote:
> On Wed, 10 Feb 2021, Daniel Vetter wrote:
>
> > On Wed, Feb 10, 2021 at 08:23:41AM +, Lee Jones wrote:
> > > On Tue, 09 Feb 2021, Julia Lawall wrote:
> > >
> > > > Use getter and setter functions, for platform_device structures and
On Thu, Feb 11, 2021 at 04:21:51PM +0800, Kevin Tang wrote:
> Daniel Vetter 于2021年2月3日周三 下午10:15写道：
>
> > On Tue, Jan 05, 2021 at 09:46:05PM +0800, Kevin Tang wrote:
> > > Adds DPU(Display Processor Unit) support for the Unisoc's display
> > subsystem.
> > > It's support multi planes, scaler,
On Wed, Feb 10, 2021 at 02:00:57PM -0800, Brian Welty wrote:
>
> On 2/9/2021 2:54 AM, Daniel Vetter wrote:
> > On Tue, Jan 26, 2021 at 01:46:25PM -0800, Brian Welty wrote:
> >> This patch adds tracking of which cgroup to make charges against for a
> >> given GEM object. We associate the current
On 2021-02-11 01:56, Rob Clark wrote:
On Wed, Feb 10, 2021 at 3:41 AM wrote:
On 2021-02-01 00:46, Rob Clark wrote:
> On Fri, Dec 18, 2020 at 2:27 AM Kalyan Thota
> wrote:
>>
>> Set the flag vblank_disable_immediate = true to turn off vblank irqs
>> immediately as soon as drm_vblank_put is
Am 11.02.21 um 16:02 schrieb Jani Nikula:
On Thu, 11 Feb 2021, Christian König wrote:
Hi guys,
I had a conflict this morning in the ttm pool while pushing an important
fix to drm-misc-fixes.
I'm not 100% sure if I correctly fixed up drm-tip. How can this be
double checked? And how can it
Hi
Am 11.02.21 um 16:05 schrieb Christian König:
Am 11.02.21 um 15:52 schrieb Thomas Zimmermann:
Hi
Am 11.02.21 um 14:16 schrieb Christian König:
Swapping bo->mem was completely unecessary. Cleanup the function which
is just a leftover from a TTM cleanup.
Yes this was introduced in a
Am 11.02.21 um 15:52 schrieb Thomas Zimmermann:
Hi
Am 11.02.21 um 14:16 schrieb Christian König:
Swapping bo->mem was completely unecessary. Cleanup the function which
is just a leftover from a TTM cleanup.
Yes this was introduced in a recent cleanup effort. Can you explain
what the code
On Thu, 11 Feb 2021, Christian König wrote:
> Hi guys,
>
> I had a conflict this morning in the ttm pool while pushing an important
> fix to drm-misc-fixes.
>
> I'm not 100% sure if I correctly fixed up drm-tip. How can this be
> double checked? And how can it be fixed if the merge has gone
On Thu, Feb 11, 2021 at 8:17 AM Christian König
wrote:
>
> Instead of swapping bo->mem just give old and new as parameters.
>
> Also drop unused parameters and code.
>
> Signed-off-by: Christian König
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.h| 3 ++-
>
On Wed, Feb 10, 2021 at 10:40 PM Bjorn Helgaas wrote:
>
> On Fri, Feb 05, 2021 at 02:36:32PM +0100, Daniel Vetter wrote:
> > We are already doing this for all the regular sysfs files on PCI
> > devices, but not yet on the legacy io files on the PCI buses. Thus far
> > no problem, but in the next
Hi
Am 11.02.21 um 14:16 schrieb Christian König:
Remove the unused evict parameter and drop swapping bo->mem.
Could you provide the same patch for vram-helpers as well?
Best regards
Thomas
Signed-off-by: Christian König
---
drivers/gpu/drm/qxl/qxl_ttm.c | 16
1 file
Hi
Am 11.02.21 um 14:16 schrieb Christian König:
Swapping bo->mem was completely unecessary. Cleanup the function which
is just a leftover from a TTM cleanup.
Yes this was introduced in a recent cleanup effort. Can you explain what
the code intends to do? It seems as if it tries to "re-unmap
Add DPCD register definitions for eDP 1.4 Multi-SST Operation.
Cc: Nischal Varide
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Jani Nikula
---
include/drm/drm_dp_helper.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
https://bugzilla.kernel.org/show_bug.cgi?id=206987
--- Comment #40 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to Jan Kokemüller from comment #39)
> Created attachment 295225 [details]
> Call DC_FP_START() / DC_FP_END() in dcn21_validate_bandwidth
>
> Could it be that
Hi Sebastian,
Am Donnerstag, 11. Februar 2021, 06:25:15 CET schrieb Sebastian Fricke:
> Hey Heiko,
>
> On 10.02.2021 12:15, Heiko Stübner wrote:
> >Hi Sebastian,
> >
> >Am Freitag, 5. Februar 2021, 15:55:56 CET schrieb Heiko Stübner:
> >> Hi Sebastian,
> >>
> >> I did some tests myself today as
(cc'ing Jani)
Am 11.02.21 um 11:01 schrieb Christian König:
Hi guys,
I had a conflict this morning in the ttm pool while pushing an important
fix to drm-misc-fixes.
I'm not 100% sure if I correctly fixed up drm-tip. How can this be
double checked? And how can it be fixed if the merge has
Instead evict round robin from each devices SYSTEM and TT domain.
v2: reorder num_pages access reported by Dan's script
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c| 31 ++-
drivers/gpu/drm/ttm/ttm_bo_util.c | 1 -
drivers/gpu/drm/ttm/ttm_device.c|
Instead of having a global lock.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 8 ++---
drivers/gpu/drm/qxl/qxl_release.c | 5 +--
drivers/gpu/drm/ttm/ttm_bo.c | 49 --
drivers/gpu/drm/ttm/ttm_device.c | 12 +++
Move the iteration of the global lru into the new function
ttm_global_swapout() and use that instead in drivers.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c| 57 -
drivers/gpu/drm/ttm/ttm_device.c| 29 +++
On 2/10/2021 6:22 AM, Jordan Crouse wrote:
Most a6xx targets have security issues that were fixed with new versions
of the microcode(s). Make sure that we are booting with a safe version of
the microcode for the target and print a message and error if not.
v2: Add more informative error
Just another leftover from a TTM cleanup.
Signed-off-by: Christian König
---
drivers/gpu/drm/nouveau/nouveau_bo.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c
b/drivers/gpu/drm/nouveau/nouveau_bo.c
index
Instead of swapping bo->mem just give old and new as parameters.
Also drop unused parameters and code.
Signed-off-by: Christian König
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h| 3 ++-
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 9 +---
drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c |
Remove the unused evict parameter and drop swapping bo->mem.
Signed-off-by: Christian König
---
drivers/gpu/drm/qxl/qxl_ttm.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_ttm.c b/drivers/gpu/drm/qxl/qxl_ttm.c
index
Swapping bo->mem was completely unecessary. Cleanup the function which
is just a leftover from a TTM cleanup.
Signed-off-by: Christian König
---
drivers/gpu/drm/drm_gem_vram_helper.c | 18 --
1 file changed, 4 insertions(+), 14 deletions(-)
diff --git
https://bugzilla.kernel.org/show_bug.cgi?id=211651
--- Comment #4 from fily1212 (ker...@fily.com.de) ---
Thank you for your reply.
Are we sure that this is outside of control of the kernel, since it works with
Kernel 5.3 and not with 5.8 and later, same drivers?
Best,
Filippo
--
You may
On Thu, Jan 28, 2021 at 11:24:13AM -0800, Matt Roper wrote:
> From: Nischal Varide
>
> If the panel is 12bpc then Dithering is not enabled in the Legacy
> dithering block , instead its Enabled after the C1 CC1 pipe post
> color space conversion.For a 6bpc pannel Dithering is enabled in
> Legacy
Hi "Christian,
url:
https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-ttm-move-swapout-logic-around/20210210-232812
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: ia64-randconfig-m031-20210209 (attached as .config)
compiler: ia64-linux-gcc (GCC) 9.3.0
If you fix
Add bridge cec_init/exit ops. These ops will be responsible for
creating and destroying the CEC adapter for the bridge that supports
CEC.
Signed-off-by: Hans Verkuil
---
drivers/gpu/drm/drm_bridge_connector.c | 23 +++
include/drm/drm_bridge.h | 31
This series improves the drm_bridge support for CEC by introducing two
new bridge ops in the first patch, and using those in the second patch.
This makes it possible to call cec_s_conn_info() and set
CEC_CAP_CONNECTOR_INFO for the CEC adapter, so userspace can associate
the CEC adapter with the
Implement the new CEC bridge ops. This makes it possible to associate
a CEC adapter with a drm connector, which helps userspace determine
with cec device node belongs to which drm connector.
Signed-off-by: Hans Verkuil
---
drivers/gpu/drm/omapdrm/dss/hdmi4.c | 28 +
Add cec clock to the dra7 and omap5 device trees.
Signed-off-by: Hans Verkuil
---
arch/arm/boot/dts/dra7.dtsi | 5 +++--
arch/arm/boot/dts/omap5.dtsi | 5 +++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index
Switch to using cec_s_phys_addr_from_edid() instead of a two-step process
of calling cec_get_edid_phys_addr() followed by cec_s_phys_addr().
Signed-off-by: Hans Verkuil
---
drivers/gpu/drm/omapdrm/dss/hdmi4.c | 13 ++---
drivers/gpu/drm/omapdrm/dss/hdmi4_cec.c | 4 ++--
This patch adds support for Newhaven's NHD-1.8-128160EF display, featuring
an Ilitek ILI9163 controller.
Signed-off-by: Daniel Mack
---
.../bindings/display/ilitek,ili9163.txt | 27 +++
drivers/gpu/drm/tiny/Kconfig | 13 +
drivers/gpu/drm/tiny/Makefile |
Add HDMI CEC support for OMAP5.
Many thanks to Tomi for helping out how to enable CEC for omap5.
Signed-off-by: Hans Verkuil
Thanks-to: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/Kconfig | 8 +
drivers/gpu/drm/omapdrm/dss/Makefile | 1 +
drivers/gpu/drm/omapdrm/dss/hdmi.h
On Wednesday, February 10th, 2021 at 11:02 PM, Mario Kleiner
wrote:
> I'll prepare patches with the same fix for libdrm and igt as well soon.
Please don't submit patches for drm_fourcc.h to downstream if they vendor the
whole file. Instead, update it from the kernel once your patch is merged
Hi guys,
I had a conflict this morning in the ttm pool while pushing an important
fix to drm-misc-fixes.
I'm not 100% sure if I correctly fixed up drm-tip. How can this be
double checked? And how can it be fixed if the merge has gone bad?
Thanks,
Christian.
Daniel Vetter 于2021年2月3日周三 下午10:15写道：
> On Tue, Jan 05, 2021 at 09:46:05PM +0800, Kevin Tang wrote:
> > Adds DPU(Display Processor Unit) support for the Unisoc's display
> subsystem.
> > It's support multi planes, scaler, rotation, PQ(Picture Quality) and
> more.
> >
> > Cc: Orson Zhai
> > Cc:
Hi Dave & Daniel -
Calming down, just a couple of Cc: stable fixes now.
drm-intel-fixes-2021-02-11:
drm/i915 fixes for v5.11 final:
- Ensure Type-C FIA is powered when initializing
- Fix overlay frontbuffer tracking
BR,
Jani.
The following changes since commit
The function drm_gem_fb_prepare_fb() is a helper for atomic modesetting,
but currently located next to framebuffer helpers. Move it to GEM atomic
helpers, rename it slightly and adopt the drivers. Same for the rsp
simple-pipe helper.
Compile-tested with x86-64, aarch64 and arm. The patch is
Hey Heiko,
On 10.02.2021 12:15, Heiko Stübner wrote:
Hi Sebastian,
Am Freitag, 5. Februar 2021, 15:55:56 CET schrieb Heiko Stübner:
Hi Sebastian,
I did some tests myself today as well and can confirm your
hdmi related finding - at least when plugged in on boot.
I tried some combinations of
74 matches
Mail list logo
