If DRM_LVDS_ENCODER=y but CONFIG_DRM_KMS_HELPER=m,
build fails:
drivers/gpu/drm/bridge/lvds-encoder.o: In function `lvds_encoder_probe':
lvds-encoder.c:(.text+0x155): undefined reference to `devm_drm_panel_bridge_add'
Reported-by: Hulk Robot
Fixes: dbb58bfd9ae6 ("drm/bridge: Fix lvds-encoder sin
On Thu, Jul 25, 2019 at 05:56:43PM -0700, Ralph Campbell wrote:
> Here are seven more patches for things I found to clean up.
> This was based on top of Christoph's seven patches:
> "hmm_range_fault related fixes and legacy API removal v3".
> I assume this will go into Jason's tree since there will
On Thu, Jul 25, 2019 at 06:12:14PM +0100, Kevin Brodsky wrote:
> It is unclear why max-memory-bandwidth should be set for CLCD on the
> fast model. Removing that property allows allocating and using 32bpp
> buffers, which may be desirable on certain platforms such as
> Android.
>
> Reported-by: Ru
On Thu, Jul 25, 2019 at 05:56:48PM -0700, Ralph Campbell wrote:
> hmm_range_fault() calls find_vma() and walk_page_range() in a loop.
> This is unnecessary duplication since walk_page_range() calls find_vma()
> in a loop already.
> Simplify hmm_range_fault() by defining a walk_test() callback funct
When fall-through warnings was enabled by default the following warning
was starting to show up:
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c: In function ‘a6xx_submit’:
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:116:7: warning: this statement may fall
through [-Wimplicit-fallthrough=]
if (priv->la
> It looks like the driver might be allocated a depth or stencil buffer
> without knowing whether it will be used. The buffer is then "grown" if
> it is needed by the GPU. The problem is it is possible for the
> application to access it later.
Hmm. I "think" you should be able to use a dummy (unba
Hi!
Dne petek, 26. julij 2019 ob 19:23:14 CEST je Andrzej Pietrasiewicz
napisal(a):
> Use the ddc pointer provided by the generic connector.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Jernej Skrabec
Thanks!
Best regards,
Jernej
> ---
> drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 6
CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by
CONFIG_PREEMPT_RT. Both PREEMPT and PREEMPT_RT require the same
functionality which today depends on CONFIG_PREEMPT.
Change the Kconfig dependency of i810 to !CONFIG_PREEMPTION so the driver
is not accidentally built on a RT kernel.
Signed-of
When fall-through warnings was enabled by default the following warning
was starting to show up:
../drivers/gpu/drm/msm/adreno/a5xx_gpu.c: In function ‘a5xx_submit’:
../drivers/gpu/drm/msm/adreno/a5xx_gpu.c:150:7: warning: this statement may fall
through [-Wimplicit-fallthrough=]
if (priv->la
On Sat, 27 Jul 2019, Daniel Vetter wrote:
> On Fri, Jul 26, 2019 at 10:25 PM Thomas Gleixner wrote:
> >
> > CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by
> > CONFIG_PREEMPT_RT. Both PREEMPT and PREEMPT_RT require the same
> > functionality which today depends on CONFIG_PREEMPT.
> >
> > Ch
When fall-through warnings was enabled by default, commit d93512ef0f0e
("Makefile: Globally enable fall-through warning"), the following
warnings was starting to show up:
../drivers/gpu/drm/arm/malidp_hw.c: In function ‘malidp_format_get_bpp’:
../drivers/gpu/drm/arm/malidp_hw.c:387:8: warning: thi
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c: In function
restore_process_worker:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:949:29: warning:
variable pdd set but not used [-Wunused-but-set-variable]
It is not used since
commit 5b8724
When fall-through warnings was enabled by default the following warning
was starting to show up:
../drivers/gpu/drm/msm/adreno/adreno_gpu.c: In function ‘adreno_submit’:
../drivers/gpu/drm/msm/adreno/adreno_gpu.c:429:7: warning: this statement may
fall
through [-Wimplicit-fallthrough=]
if (p
On 25/07/2019 18:40, Alyssa Rosenzweig wrote:
Sorry, I was being sloppy again![1] I meant CPU mmapped.
No worries, just wanted to check :)
Apparently the blob in some cases creates a SAME_VA GROW_ON_GPF buffer -
since SAME_VA means permanently mapped on the CPU this translated to
mmapping a H
On Wed, Jul 24, 2019 at 4:24 PM John Stultz wrote:
>
> On Wed, Jul 24, 2019 at 1:18 PM John Stultz wrote:
> >
> > On Wed, Jul 24, 2019 at 12:36 PM Laura Abbott wrote:
> > >
> > > On 7/17/19 12:31 PM, Alexander Popov wrote:
> > > > Hello!
> > > >
> > > > The syzkaller [1] has a trouble with fuzzi
Hello,
I am happy to see this discussion.
I like Noralf's late work to move mipi_dbi to drm/ and remove tinydrm.
This helps to simplify implementation and maintenance of drivers for
displays that conform to MIPI_DBI set of commands,
no matter if they use MIPI_DBI to transfer the image data or not.
It is normal that binary syncobj replaces the underlying fence.
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/drm_syncobj.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_syncobj.c b/drivers/gpu/drm/drm_syncobj.c
index 929f7c64f9a2..bc7ec1679e4d 100644
--- a/drivers
On Tue, 23 Jul 2019, Kai-Heng Feng wrote:
> Hi,
>
> Currently, OLED panel brightness [1] is not supported.
As a general statement this is not true, and not backed up by the
referenced bug. We just don't know how brightness is controlled on that
particular laptop, because it apparently uses a prop
On Thu, 25 Jul 2019, Daniel Vetter wrote:
> On Thu, Jul 25, 2019 at 03:35:40PM +0800, Kai-Heng Feng wrote:
>> The next question is, how do we change the brightness level for OLED
>> displays? Is changing gamma value a good way to do it?
>
> There's no overall amplifier knob to set general brightne
https://bugs.freedesktop.org/show_bug.cgi?id=111244
Michel Dänzer changed:
What|Removed |Added
Attachment #144901|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=111244
Michel Dänzer changed:
What|Removed |Added
CC||nicholas.kazlaus...@amd.com
--- Comment
On Wed, 24 Jul 2019, Andrzej Pietrasiewicz wrote:
> Allow passing ddc adapter pointer to the init function. Even if
> drm_connector_init() sometime in the future decides to e.g. memset() all
> connector fields to zeros, the newly added function ensures that at its
> completion the ddc member of co
https://bugs.freedesktop.org/show_bug.cgi?id=111234
Michel Dänzer changed:
What|Removed |Added
CC||nicholas.kazlaus...@amd.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=111229
Michel Dänzer changed:
What|Removed |Added
Attachment #144877|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=111229
Michel Dänzer changed:
What|Removed |Added
Attachment #144878|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=111232
Michel Dänzer changed:
What|Removed |Added
Attachment #144891|text/x-log |text/plain
mime type|
If CONFIG_DRM_TOSHIBA_TC358764=y but CONFIG_DRM_KMS_HELPER=m,
building fails:
drivers/gpu/drm/bridge/tc358764.o:(.rodata+0x228): undefined reference to
`drm_atomic_helper_connector_reset'
drivers/gpu/drm/bridge/tc358764.o:(.rodata+0x240): undefined reference to
`drm_helper_probe_single_connector
https://bugs.freedesktop.org/show_bug.cgi?id=111228
--- Comment #3 from Michel Dänzer ---
>From the attached bug report log:
*** /usr/share/X11/xorg.conf.d/10-amdgpu.conf
*** ls: -rw-r--r-- 1 root root 98 2019-07-12 20:45:36.635624123 +1000
/usr/share/X11/xorg.conf.d/10-amdgpu.conf
Section "Outp
On Fri, 2019-07-26 at 19:23 +0200, Andrzej Pietrasiewicz wrote:
> Use the ddc pointer provided by the generic connector.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Philipp Zabel
Thanks!
regards
Philipp
> ---
> drivers/gpu/drm/imx/imx-ldb.c | 7 ---
> 1 file changed, 4 insertions
On Fri, 2019-07-26 at 19:23 +0200, Andrzej Pietrasiewicz wrote:
> Use the ddc pointer provided by the generic connector.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Philipp Zabel
regards
Philipp
> ---
> drivers/gpu/drm/imx/imx-tve.c | 6 --
> 1 file changed, 4 insertions(+), 2 del
https://bugs.freedesktop.org/show_bug.cgi?id=111244
--- Comment #4 from csp...@verizon.net ---
The first bisect pointed to a merge commit so the second was done to bisect
within the merged commits.
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=111228
--- Comment #4 from Maik Freudenberg ---
Both amdgpu and modesetting driver were tested, same effect.
Most notewothy in the non-prime modesetting driver case is this:
[ 5.477] (EE) modeset(0): [DRI2] No driver mapping found for PCI device
0x
https://bugs.freedesktop.org/show_bug.cgi?id=111211
--- Comment #5 from Bráulio Barros de Oliveira ---
The issue might appear only after suspend and resume of the laptop.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri
https://bugs.freedesktop.org/show_bug.cgi?id=111228
Maik Freudenberg changed:
What|Removed |Added
Summary|PRIME output screen satys |PRIME output screen stays
Hi Pei,
On Sat, Jul 27, 2019 at 10:21:09PM +0800, Pei Hsuan Hung wrote:
> Signed-off-by: Pei Hsuan Hung
> Cc: triv...@kernel.org
> ---
> arch/powerpc/kernel/eeh.c | 2 +-
> arch/powerpc/platforms/cell/spufs/switch.c | 4 ++--
> drivers/extcon/extcon-rt8973a.c
On Mon, 29 Jul 2019, Kai-Heng Feng wrote:
> at 16:26, Jani Nikula wrote:
>
>> On Tue, 23 Jul 2019, Kai-Heng Feng wrote:
>>> Hi,
>>>
>>> Currently, OLED panel brightness [1] is not supported.
>>
>> As a general statement this is not true, and not backed up by the
>> referenced bug. We just don't
https://bugs.freedesktop.org/show_bug.cgi?id=111244
--- Comment #5 from Michel Dänzer ---
(In reply to cspack from comment #4)
> The first bisect pointed to a merge commit so the second was done to bisect
> within the merged commits.
That doesn't invalidate my previous comment. :) git bisect ide
Hi Anders,
On Fri, Jul 26, 2019 at 01:27:41PM +0200, Anders Roxell wrote:
> When fall-through warnings was enabled by default, commit d93512ef0f0e
> ("Makefile: Globally enable fall-through warning"), the following
> warnings was starting to show up:
>
> ../drivers/gpu/drm/arm/malidp_hw.c: In fun
On Fri, Jul 26, 2019 at 06:15:46PM +0200, Daniel Vetter wrote:
> On Fri, Jul 26, 2019 at 4:44 PM Brian Starkey wrote:
> >
> > On Fri, Jul 26, 2019 at 04:23:56PM +0200, Daniel Vetter wrote:
> > > On Fri, Jul 26, 2019 at 08:13:00AM +, Lowry Li (Arm Technology China)
> > > wrote:
> > > > Current
On 7/29/19 4:58 AM, Liviu Dudau wrote:
>> case MW_RESTART:
>> drm_writeback_signal_completion(&malidp->mw_connector,
>> 0);
>> -/* fall through to a new start */
>
> It's a shame that the compiler throws a warning here, it would've been rea
Hi Anders,
On 7/26/19 6:28 AM, Anders Roxell wrote:
> When fall-through warnings was enabled by default the following warnings
> was starting to show up:
>
> ../drivers/video/fbdev/sh_mobile_lcdcfb.c: In function
> ‘sh_mobile_lcdc_channel_fb_init’:
> ../drivers/video/fbdev/sh_mobile_lcdcfb.c:208
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #52 from Peter Hercek ---
I'm getting hangs-up with kernels 5.2.3 (often) and 5.1.15 (less often).
Radeon VII with 3 monitors. Each monitor connected through DP.
--
You are receiving this mail because:
You are the assignee for the
On Thu, Jul 25, 2019 at 5:41 PM maxime.rip...@free-electrons.com
wrote:
>
> On Thu, Jul 25, 2019 at 11:05:23AM +, Oleksandr Suvorov wrote:
> >
> > Even in source code of this driver there is an author's description:
> > /*
> > * Even if we have an I2C bus, we can't assume that the cab
Hi,
On Thu, Jul 25, 2019 at 06:02:12PM -0400, Paul Cercueil wrote:
> It has been replaced with the more mature ingenic-battery driver.
>
> Signed-off-by: Paul Cercueil
> Tested-by: Artur Rojek
> ---
Acked-by: Sebastian Reichel
-- Sebastian
> drivers/power/supply/Kconfig | 11 -
>
https://bugs.freedesktop.org/show_bug.cgi?id=111248
Bug ID: 111248
Summary: Navi10 Font rendering issue in Overwatch
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity
On Fri, Jul 26, 2019 at 12:02 AM Paul Cercueil wrote:
>
> Hi,
>
> This patchset converts the Qi LB60 MIPS board to devicetree and makes it
> use all the shiny new drivers that have been developed or updated
> recently.
>
> All the crappy old drivers and custom code can be dropped since they
> have
https://bugs.freedesktop.org/show_bug.cgi?id=110488
yanhua <78666...@qq.com> changed:
What|Removed |Added
CC||dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=110488
--- Comment #2 from yanhua <78666...@qq.com> ---
I encounter this bug too. it causes my gpu failed to any thing.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111234
--- Comment #2 from Nicholas Kazlauskas ---
This is almost certainly a duplicate of:
https://bugzilla.kernel.org/show_bug.cgi?id=204181
I think something in KDE plasma changed recently for how multi monitor support
is handled and how commits a
https://bugs.freedesktop.org/show_bug.cgi?id=111229
--- Comment #7 from weden...@yandex.ru ---
Created attachment 144907
--> https://bugs.freedesktop.org/attachment.cgi?id=144907&action=edit
kernel 5.1
I've narrowed it down to kernel 5.1. There are a lot of amdgpu changes in 5.1
(Vega related c
https://bugs.freedesktop.org/show_bug.cgi?id=107559
--- Comment #7 from g.grazi...@gmail.com ---
Similar problem over here: everything works fine with amdgpu.dc=0. Without it
the colors are way darker.
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugzilla.kernel.org/show_bug.cgi?id=204363
Bug ID: 204363
Summary: EDID from Acer P1266 rejected as invalid
Product: Drivers
Version: 2.5
Kernel Version: 5.2.4
Hardware: All
OS: Linux
Tree: Mainline
On Fri, 19 Jul 2019, "Koenig, Christian" wrote:
> Am 18.07.19 um 18:46 schrieb Chris Wilson:
>> Quoting Sam Ravnborg (2019-07-18 17:14:58)
>>> drm_print.h used DRM_NAME - thus adding a dependency from
>>> include/drm/drm_print.h => uapi/drm/drm.h
>>>
>>> Hardcode the name "drm" to break this depen
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #63 from Talha Khan ---
I updated my kernel to 5.1.19, and the firwmare files were updated, but I
wasn't able to boot. I had to boot back into 5.1.16 and perform the workaround
before being able to boot into 5.1.19.
--
You are rece
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #12 from Pierre-Eric Pelloux-Prayer
---
Thanks for the bug report.
I could reproduce the bug using the provided apitrace, both on a Ryzen platform
and on a Vega Mobile laptop (can't reproduce on Navi).
Using MESA_DEBUG=flush or AM
https://bugs.freedesktop.org/show_bug.cgi?id=109456
--- Comment #8 from libgra...@gmail.com ---
Got back to this again recently and can confirm it's fixed in Qemu git (for
4.1) now.
Many thanks :)
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=109456
libgra...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 2019-07-26 11:06 p.m., Sam Ravnborg wrote:
> DRM_WAIT_ON() is from the deprecated drm_os_linux header and
> the modern replacement is the wait_event_*.
>
> The return values differ, so a conversion is needed to
> keep the original interface towards userspace.
> Introduced a switch/case to make
On Sun, 14 Jul 2019 16:30:08 +0530
Ramalingam C wrote:
> This patch adds a DRM ENUM property to the selected connectors.
> This property is used for mentioning the protected content's type
> from userspace to kernel HDCP authentication.
>
> Type of the stream is decided by the protected content
https://bugzilla.kernel.org/show_bug.cgi?id=204365
Bug ID: 204365
Summary: amdgpu crashes when using parameter
"drm.edid_firmware"
Product: Drivers
Version: 2.5
Kernel Version: 5.2.4
Hardware: All
OS: Li
On Fri, Jul 26, 2019 at 06:36:01PM +0200, Maxime Ripard wrote:
> > +
> > + dvdd12-supply:
> > +maxItems: 1
> > +description: Regulator for 1.2V digital core power.
> > +$ref: /schemas/types.yaml#/definitions/phandle
> > +
> > + dvdd25-supply:
> > +maxItems: 1
> > +description:
Hi Sébastien,
On Mon, Jul 29, 2019 at 11:14 AM Sébastien Szymanski
wrote:
> config DRM_MXSFB
> - tristate "i.MX23/i.MX28/i.MX6SX MXSFB LCD controller"
> + tristate "i.MX23/i.MX28/i.MX6SX/i.MX6UL MXSFB LCD controller"
This IP is also found on i.MX6SL, i.MX7D, i.MX7S, i.MX8M, i.MX8QX
> >>
> >> Even then it so useless (which drm driver is this message for???) that I
> >> want to remove them all :(
> >
> > Yeah, agree. I mean it is nice if the core drm functions use a prefix
> > for debug output.
> >
> > But I actually don't see the point for individual drivers.
>
> We should a
Hi Sébastien,
On Mon, Jul 29, 2019 at 11:27:37AM -0300, Fabio Estevam wrote:
> Hi Sébastien,
>
> On Mon, Jul 29, 2019 at 11:14 AM Sébastien Szymanski
> wrote:
>
> > config DRM_MXSFB
> > - tristate "i.MX23/i.MX28/i.MX6SX MXSFB LCD controller"
> > + tristate "i.MX23/i.MX28/i.MX6SX/i.M
From: Liviu Dudau
Add the names of the kernel modules for the Arm display drivers
so that tests inside libDRM can auto-detect their presence.
Signed-off-by: Liviu Dudau
---
tests/util/kms.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/util/kms.c b/tests/util/kms.c
index dd1bbee
Am 29.07.19 um 16:35 schrieb Sam Ravnborg:
Even then it so useless (which drm driver is this message for???) that I
want to remove them all :(
>>> Yeah, agree. I mean it is nice if the core drm functions use a prefix
>>> for debug output.
>>>
>>> But I actually don't see the point for ind
On Fri, 2019-07-05 at 19:17 +0200, Lucas Stach wrote:
> This reworks the MMU handling to make it possible to have multiple MMU
> contexts.
> A context is basically one instance of GPU page tables. Currently we have one
> set of page tables per GPU, which isn't all that clever, as it has the
> foll
On Fri, 2019-07-05 at 19:17 +0200, Lucas Stach wrote:
> Move buffer setup and starting of the FE loop in the kernel ringbuffer
> into a separate function. This is a preparation to start the FE later
> in the submit process.
>
> Signed-off-by: Lucas Stach
> ---
> drivers/gpu/drm/etnaviv/etnaviv_g
On Fri, 2019-07-05 at 19:17 +0200, Lucas Stach wrote:
> In preparation to having a context per process, etnaviv_gem_mapping_get
> should not use the current GPU context, but needs to be told which
> context to use.
>
> Signed-off-by: Lucas Stach
> ---
> drivers/gpu/drm/etnaviv/etnaviv_gem.c
Hi Sam,
On Mon, Jul 29, 2019 at 11:37 AM Sam Ravnborg wrote:
> Could we throw a COMPILE_TEST in the mix so we get better build
> coverage too?
There is no architecture dependency to build this driver, so we
already have build coverage for it.
Regards,
Fabio Estevam
___
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #13 from Pierre-Eric Pelloux-Prayer
---
Using AMD_DEBUG=nodpbb "fixes" the problem.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dr
https://bugs.freedesktop.org/show_bug.cgi?id=111232
--- Comment #1 from Alex Deucher ---
Can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.
On Tue, Jun 18, 2019 at 09:10:40AM +0100, james qian wang (Arm Technology
China) wrote:
> struct drm_display_mode contains two copies of timings.
> - plain timings.
> - hardware timings, the ones with "crtc_" prefix.
> According to the definition, update komeda to use the hardware timing.
>
> Sig
https://bugs.freedesktop.org/show_bug.cgi?id=110968
--- Comment #3 from Jeremy Newton ---
This is not a Ubuntu issue, we do this purposely.
Let me discuss internally and I can try to get a better solution.
--
You are receiving this mail because:
You are the assignee for the bug.___
On Tue, Jun 18, 2019 at 09:10:49AM +0100, james qian wang (Arm Technology
China) wrote:
> Komeda HW can support dual-link which splits display frame to two halves
> (left/link0, right/link1) and output them by two output links.
> Due to the halved pixel rate of each link, the pxlclk of dual-link c
https://bugs.freedesktop.org/show_bug.cgi?id=108994
Jeremy Newton changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=107826
Jeremy Newton changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=108883
Jeremy Newton changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #9 from John Francis ---
I am still seeing this error on kernel 5.2.2. I think it happens when I switch
away the monitors to another host on the KVM switch.
Switching back later, I get only 1 display, problematic as some windows are
https://bugzilla.kernel.org/show_bug.cgi?id=204363
Adam Jackson (a...@redhat.com) changed:
What|Removed |Added
CC||a...@redhat.com
--- Comm
On 2019-07-29 at 17:20:40 +0300, Pekka Paalanen wrote:
> On Sun, 14 Jul 2019 16:30:08 +0530
> Ramalingam C wrote:
>
> > This patch adds a DRM ENUM property to the selected connectors.
> > This property is used for mentioning the protected content's type
> > from userspace to kernel HDCP authentic
https://bugs.freedesktop.org/show_bug.cgi?id=108882
--- Comment #1 from Jeremy Newton ---
It sounds like fglrx was not cleaned up properly.
Unfortunately I'm not sure there's much we can do here.
--
You are receiving this mail because:
You are the assignee for the bug._
Move basic members of ttm_mem_type_manager into a new DRM memory region
structure. The idea is for this base structure to be nested inside
the TTM structure and later in Intel's proposed intel_memory_region.
As comments in the code suggest, the following future work can extend
the usefulness of t
This RFC series is first implementation of some ideas expressed
earlier on dri-devel [1].
Some of the goals (open for much debate) are:
- Create common base structure (subclass) for memory regions (patch #1)
- Create common memory region types (patch #2)
- Create common set of memory_region
Introduce DRM memory region types to be common for both drivers using
TTM and for i915. For now, TTM continues to define it's own set but
uses the DRM base definitions.
Signed-off-by: Brian Welty
---
include/drm/drm_mm.h| 8
include/drm/ttm/ttm_placement.h | 8
2 f
Some fields are deleted from intel_memory_region in favor of instead
using the new nested drm_mem_region structure.
Note, this is based upon unmerged i915 series [1] in order to show how
i915 might begin to integrate the proposed drm_mem_region.
[1] https://lists.freedesktop.org/archives/intel-gf
Hi Richard,
Le lun. 29 juil. 2019 à 7:23, Richard Weinberger
a écrit :
On Fri, Jul 26, 2019 at 12:02 AM Paul Cercueil
wrote:
Hi,
This patchset converts the Qi LB60 MIPS board to devicetree and
makes it
use all the shiny new drivers that have been developed or updated
recently.
All
Hi Christian.
On Mon, Jul 29, 2019 at 03:28:15PM +, Koenig, Christian wrote:
> Am 29.07.19 um 16:35 schrieb Sam Ravnborg:
> Even then it so useless (which drm driver is this message for???) that I
> want to remove them all :(
> >>> Yeah, agree. I mean it is nice if the core drm funct
Hi Fabio.
On Mon, Jul 29, 2019 at 12:51:08PM -0300, Fabio Estevam wrote:
> Hi Sam,
>
> On Mon, Jul 29, 2019 at 11:37 AM Sam Ravnborg wrote:
>
> > Could we throw a COMPILE_TEST in the mix so we get better build
> > coverage too?
>
> There is no architecture dependency to build this driver, so w
Hi Brian.
Small nit below - did not try to understand your patch.
Sam
> diff --git a/include/drm/drm_mm.h b/include/drm/drm_mm.h
> index 2c3bbb43c7d1..3d123eb10d62 100644
> --- a/include/drm/drm_mm.h
> +++ b/include/drm/drm_mm.h
> @@ -43,6 +43,8 @@
> #include
> #include
> #include
- Ursprüngliche Mail -
>> Was this series tested with the Ben Nanonote device?
>> I have one of these and from time to time I upgrade the kernel on it.
>
> Yes! Artur (Cc'd) tested it.
>
> You can test it yourself, after merging this patchset with:
> https://git.kernel.org/pub/scm/linux/k
https://bugs.freedesktop.org/show_bug.cgi?id=111244
--- Comment #6 from csp...@verizon.net ---
I see your point, and you are correct. It seems the issue is not 100%
reproducible. I will redo the bisect and test more thoroughly. Thank you.
--
You are receiving this mail because:
You are the assig
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #14 from deltasquared ---
The apitrace no longer causes issues on my system either if I use
AMD_DEBUG=nodpbb . I also decided to try this on minetest and *so far* (bearing
in mind the issue was indetermistic in the first place, so a
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #53 from Anthony Rabbito ---
Interesting, on 5.2.x with 2 monitors hooked up via HDMI and DP it behaves 75%
of the time with most issues coming from xinit or sleep. Hopefully 5.3 will
contain fixes
--
You are receiving this mail be
From: Jérôme Glisse
commit 5e383a9798990c69fc759a4930de224bb497e62c upstream.
The debugfs take reference on fence without dropping them.
Signed-off-by: Jérôme Glisse
Cc: Christian König
Cc: Daniel Vetter
Cc: Sumit Semwal
Cc: linux-me...@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Cc
https://bugs.freedesktop.org/show_bug.cgi?id=109834
Jeremy Newton changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110405
--- Comment #1 from Jeremy Newton ---
Can you try a newer driver? 18.30 is pretty old and likely doesn't support
18.04.2.
--
You are receiving this mail because:
You are the assignee for the bug.___
From: Josef Lusticky
Add driver for Ilitek ILI9341 panels in parallel RGB mode
Signed-off-by: Josef Lusticky
---
MAINTAINERS | 6 +
drivers/gpu/drm/panel/Kconfig| 9 +
drivers/gpu/drm/panel/Makefile | 1 +
drivers/gpu/drm/pan
Embed mipi_dbi in struct ili9341.
Rebase on moved mipi-dbi, rename variable name.
Add backlight_device to panel struct.
mipi_dbi_hw_reset() already has a NULL check on the reset gpio.
Prepare for more panels by reworking ili9341_config.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/panel/pan
= mipi_dbi_debugfs_init,
+ .name = "drm_mipi_dbi",
+ .desc = "DRM MIPI DBI",
+ .date = "20190729",
+ .major = 1,
+ .minor = 0,
+};
+
+/**
+ * drm
1 - 100 of 154 matches
Mail list logo
