Create variable for the list length limit. Serves as documentation,
also allows to make it a module parameter if needed.
Also add a total size limit.
Signed-off-by: Gerd Hoffmann
---
drivers/dma-buf/udmabuf.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/driver
Reported-by: Laurent Pinchart
Signed-off-by: Gerd Hoffmann
---
drivers/dma-buf/udmabuf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma-buf/udmabuf.c b/drivers/dma-buf/udmabuf.c
index 19bd918209..ec22f203b5 100644
--- a/drivers/dma-buf/udmabuf.c
+++ b/drivers/dma
Hi,
On 11-09-18 08:48, Nicholas Mc Guire wrote:
On Mon, Sep 10, 2018 at 08:30:38PM +0200, Hans de Goede wrote:
Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
drm_dev_register.") replaced the obsolere drm_get_pci_dev() with
normal pci probe and remove functions.
But the new vbox
https://bugzilla.kernel.org/show_bug.cgi?id=199619
--- Comment #11 from Elmar Stellnberger (estel...@elstel.org) ---
persists with 4.19.0-rc2+
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
Hi,
> > +#define UDMABUF_CREATE _IOW('u', 0x42, struct udmabuf_create)
>
> Why do you start at 0x42 if you reserve the 0x40-0x4f range ?
No particular strong reason, just that using 42 was less boring than
starting with 0x40.
> > +#define UDMABUF_CREATE_LIST _IOW('u', 0x43, struct udma
On 10/09/18 20:44, Tony Lindgren wrote:
>> I want to make it clear that I don't want to claim any privilege in getting
>> patches merged first. I am however worried that, without an easy way to test
>> DSI support, and without enough time to focus on it, I would break whatever
>> would be merge
Hey Dave,
A bunch of fixes for MST/runpm problems and races, as well as fixes
for issues that prevent more recent laptops from booting.
Thanks,
Ben.
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Gi
Russell (or someone else), can you Ack this patch? I'd like to get this
for 4.20.
Thanks!
Hans
On 08/27/2018 02:28 PM, Hans Verkuil wrote:
> The CEC_TX_STATUS_MAX_RETRIES should be set for errors only to
> prevent the CEC framework from retrying the transmit. If the
> transmit was succes
Hi,
On 11-09-18 01:08, Steve Longerbeam wrote:
Hi Hans,
On 09/10/2018 11:30 AM, Hans de Goede wrote:
Commit 2408898e3b6c ("staging: vboxvideo: Add page-flip support") only
calls vbox_crtc_do_set_base() on page-flips, but despite that function's
name it only pins the new fb, unpins the old fb
> > > > +#include
> > > > +#include
> > > > +
> > > > +/**
> > > > + * DOC: overview
> > > > + *
> > > > + * FB_DAMAGE_CLIPS is an optional plane property which provides a
> > > means to
> > > > + * specify a list of damage rectangles on a plane in framebuffer
> > > coordinates of
> > > > + * th
https://bugs.freedesktop.org/show_bug.cgi?id=103300
--- Comment #4 from Ian Bruene ---
(In reply to Timothy Arceri from comment #2)
> If so do you think you could get an apitrace [1] of the problem?
>
> [1] https://github.com/apitrace/apitrace/wiki/Steam
I tried today and was unable to get a tr
>
> On Thu, 6 Sep 2018 21:36:51 +
> Deepak Singh Rawat wrote:
>
> > >
> > > - Why no input validation on the damage clips against the framebuffer
> > > size? Ime not validating just leads to funny driver bugs down the road,
> > > so what's the use-case you have in mind here?
> >
> > My
On 9/5/18 2:37 PM, Rob Herring wrote:
#ifdef CONFIG_NOT_COHERENT_CACHE
- np = of_find_node_by_type(NULL, "cpu");
+ np = of_get_cpu_node(0, NULL);
This #ifdef means that it's only compiled on an MPC5121, which is a very
dead platform. of_get_cpu_node() looks okay to me, but I'm g
On Mon, Sep 10, 2018 at 10:55 AM Alex Deucher wrote:
>>
>> Only specific N value (0x8000) would be acceptable for LG
>> LP140WF6-SPM1 eDP panel which is running at asynchronous clock mode.
>> With the other N value, it will enter BITS mode and display black
>> screen. This patch series set const
Hi Peter,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc3 next-20180910]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
https://bugs.freedesktop.org/show_bug.cgi?id=104906
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEEDINFO
https://bugzilla.kernel.org/show_bug.cgi?id=201067
--- Comment #2 from Nick Sarnie (sar...@gentoo.org) ---
Hi Nicholas,
Thank you for the fast response.
I can confirm the patch fixes the issue.
If you intend to submit this:
Tested-by: Nick Sarnie
Thanks,
Sarnex
--
You are receiving this ma
https://bugs.freedesktop.org/show_bug.cgi?id=107889
--- Comment #4 from Alex Deucher ---
Can you bisect? Also please attach your dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-dev
https://bugs.freedesktop.org/show_bug.cgi?id=107889
Alex Deucher changed:
What|Removed |Added
Attachment #141511|text/x-log |text/plain
mime type|
On Mon, Sep 10, 2018 at 10:55 AM Lee, Shawn C wrote:
>
> Only specific N value (0x8000) would be acceptable for LG
> LP140WF6-SPM1 eDP panel which is running at asynchronous
> clock mode. With the other N value, it will enter BITS mode
> and display black screen. This patch series set constant N
>
Hi,
On Mon, Sep 10, 2018 at 03:24:37PM +0300, Laurent Pinchart wrote:
> On Monday, 10 September 2018 14:59:23 EEST Tomi Valkeinen wrote:
> > On 30/08/18 12:04, Pavel Machek wrote:
> > > There's neat series of patches on
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
https://bugzilla.kernel.org/show_bug.cgi?id=201015
--- Comment #7 from Aleksandr Mezin (mezin.alexan...@gmail.com) ---
(In reply to Nicholas Kazlauskas from comment #6)
> I'd imagine you're probably running GNOME on Wayland from that setup
> environment.
>
> The patch seems to fix the null pointe
On Mon, Sep 10, 2018 at 06:29:46PM +0100, Alexandru Gheorghe wrote:
> DRM_MODE_REFLECT_X and DRM_MODE_REFLECT_Y meaning seems a bit unclear
> to me, so try to clarify that with a bit of ascii graphics.
>
> Changes since v1:
> - Move the ascii graphics in the kerneldoc where all plane
> prope
On Mon, Sep 10, 2018 at 03:02:16PM +0300, Ville Syrjälä wrote:
> On Fri, Sep 07, 2018 at 02:46:21PM -0700, Satish Kumar Nagireddy wrote:
> > The requirement is to render interlaced alternate buffers. In case of
> > alternate, top field and bottom field are in two different buffers.
> >
> > The que
https://bugs.freedesktop.org/show_bug.cgi?id=107880
Marvin Damschen changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Mon, Sep 10, 2018 at 09:50:03AM +0100, Brian Starkey wrote:
> Hi,
>
> On Fri, Sep 07, 2018 at 09:28:44PM +0200, Daniel Vetter wrote:
> > On Fri, Sep 07, 2018 at 01:45:36PM +0100, Brian Starkey wrote:
> > > Hi Daniel,
> > >
> > > On Fri, Aug 31, 2018 at 10:17:30AM +0200, Daniel Vetter wrote:
>
On Tue, Jul 31, 2018 at 02:07:05PM -0700, Manasi Navare wrote:
> From: "Srivatsa, Anusha"
>
> DSC has some Rate Control values that remain constant
> across all configurations. These are as per the DSC
> standard.
>
> v3:
> * Define them in drm_dsc.h as they are
> DSC constants (Manasi)
> v2:
>
Hi Jérôme,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc3 next-20180910]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Jérôme,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc3 next-20180910]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
https://bugzilla.kernel.org/show_bug.cgi?id=201015
--- Comment #6 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
I'd imagine you're probably running GNOME on Wayland from that setup
environment.
The patch seems to fix the null pointer deference but you're probably getting a
black scre
https://bugs.freedesktop.org/show_bug.cgi?id=107891
Bug ID: 107891
Summary: [wine, regression, bisected] RAGE, Wolfenstein The New
Order hangs in menu
Product: Mesa
Version: 18.2
Hardware: Other
OS: All
Hi Jérôme,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc3 next-20180910]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Jérôme,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc3 next-20180910]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
https://bugzilla.kernel.org/show_bug.cgi?id=201015
--- Comment #5 from Aleksandr Mezin (mezin.alexan...@gmail.com) ---
Created attachment 278427
--> https://bugzilla.kernel.org/attachment.cgi?id=278427&action=edit
Kernel log, 2 suspend-resume attempts, second one failed
(In reply to Nicholas Ka
Commit 2408898e3b6c ("staging: vboxvideo: Add page-flip support") only
calls vbox_crtc_do_set_base() on page-flips, but despite that function's
name it only pins the new fb, unpins the old fb and sets
vbox_crtc->fb_offset. It does not program the hardware to scan out at the
new vbox_crtc->fb_offset
Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
drm_dev_register.") replaced the obsolere drm_get_pci_dev() with
normal pci probe and remove functions.
But the new vbox_pci_probe() is missing a pci_enable_device() call,
causing interrupts to not be delivered. This causes resizes of
https://bugzilla.kernel.org/show_bug.cgi?id=201015
--- Comment #4 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
Created attachment 278425
--> https://bugzilla.kernel.org/attachment.cgi?id=278425&action=edit
0001-drm-amd-display-Add-null-checks-to-surface-update-in.patch
I'm unable
https://bugs.freedesktop.org/show_bug.cgi?id=107880
--- Comment #7 from jam...@amd.com ---
Dmesg shows: Found VCN firmware Version: 1.24 Family ID: 18.
It is really old.
Please update with latest vcn firmware for raven (1.73)
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware
DRM_MODE_REFLECT_X and DRM_MODE_REFLECT_Y meaning seems a bit unclear
to me, so try to clarify that with a bit of ascii graphics.
Changes since v1:
- Move the ascii graphics in the kerneldoc where all plane
properties are already documented and make sure it's properly
rendered, suggestes
When doing suspend/resume drivers usually use the
drm_atomic_helper_suspend/drm_atomic_helper_resume pair for saving the
state and then re-comitting it.
The problem is that drm_crtc_state has a bool field called
color_mgmt_changed, which mali-dp and other drivers uses it to detect
if coefficients
https://bugs.freedesktop.org/show_bug.cgi?id=107889
--- Comment #3 from Mauro Carvalho Chehab ---
Created attachment 141511
--> https://bugs.freedesktop.org/attachment.cgi?id=141511&action=edit
Xorg logs with Kernel 4.17.3 + drm-next patches submitted for 4.18-rc1
--
You are receiving this ma
https://bugs.freedesktop.org/show_bug.cgi?id=107889
--- Comment #2 from Mauro Carvalho Chehab ---
Created attachment 141510
--> https://bugs.freedesktop.org/attachment.cgi?id=141510&action=edit
Xorg logs with Kernel 4.18.5
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freedesktop.org/show_bug.cgi?id=107889
--- Comment #1 from Mauro Carvalho Chehab ---
Created attachment 141509
--> https://bugs.freedesktop.org/attachment.cgi?id=141509&action=edit
output of xrandr
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=107889
Bug ID: 107889
Summary: colors are wrong on one screen with Radeon RX Vega M
GL and Kernel 4.18
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS:
https://bugzilla.kernel.org/show_bug.cgi?id=201067
--- Comment #1 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
Created attachment 278423
--> https://bugzilla.kernel.org/attachment.cgi?id=278423&action=edit
Patch that reverts the 15% reduction in set dispclk
While I can't reproduce
https://bugs.freedesktop.org/show_bug.cgi?id=107581
--- Comment #22 from Benjamin Hodgetts ---
Just an FYI, testing with Mesa GIT this morning and the coloured space nebulae
are being rendered correctly as well. Additionally the weird garbage/distortion
below the "NEXT" notification when you firs
Hi Heiko,
CEC is not working when CEC 5V is enabled
On 2018-09-10 11:22, Heiko Stuebner wrote:
> The rk3328 uses a dw-hdmi controller with an external hdmi phy from
> Innosilicon which uses the generic phy framework for access.
> Add the necessary data and the compatible for the rk3328 to the
>
On Tue, 14 Aug 2018, Enric Balletbo i Serra wrote:
> The "atomic" API allows us to configure PWM period and duty_cycle and
> enable it in one call.
>
> The patch also moves the pwm_init_state just before any use of the
> pwm_state struct, this fixes a potential bug where pwm_get_state
> can be ca
Only specific N value (0x8000) would be acceptable for LG
LP140WF6-SPM1 eDP panel which is running at asynchronous
clock mode. With the other N value, it will enter BITS mode
and display black screen. This patch series set constant N
value for specific sink/branch device that would cover
similar is
Some DP dongles in particular seem to be fussy about too large
link M/N values. Set specific value for N divider can resolve
this issue per dongle vendor's comment. So configure N as
constant value (0x8000) to instead of reduce M/N formula when
specific DP dongle connected.
Cc: Jani Nikula
Cc: Co
The N value was computed by kernel driver that based on synchronous clock
mode. But only specific N value (0x8000) would be acceptable for
LG LP140WF6-SPM1 eDP panel which is running at asynchronous clock mode.
With the other N value, Tcon will enter BITS mode and display black screen.
Add this pan
DP quirk list just compare sink or branch device's OUI so far.
That means particular vendor's products will be applied specific
change. This change would confirm device_id the same or not.
Then driver can implement some changes for branch/sink device
that really need additional WA.
Cc: Jani Nikula
https://bugs.freedesktop.org/show_bug.cgi?id=68059
--- Comment #14 from Alex Deucher ---
dpm has been enabled by default for just about all card except the original
r6xx asics for years now.
--
You are receiving this mail because:
You are the assignee for the bug.___
Hi Maxime,
On Monday, 10 September 2018 17:16:03 EEST Maxime Ripard wrote:
> On Fri, Sep 07, 2018 at 05:26:29PM +0300, Laurent Pinchart wrote:
> + */
> +int phy_mipi_dphy_get_default_config(unsigned long pixel_clock,
> + unsigned int bpp,
> +
Hi Ayan,
On Mon, Sep 10, 2018 at 03:11:34PM +0100, Ayan Halder wrote:
On Fri, Aug 31, 2018 at 10:17:30AM +0200, Daniel Vetter wrote:
On Thu, Aug 23, 2018 at 04:23:41PM +0100, Brian Starkey wrote:
[snip]
>unsigned int min_size;
> + u8 bpp = drm_format_info_plane_bpp(fb->
On Mon, May 28, 2018 at 10:27 AM Emil Lundmark wrote:
>
> This fixes a NULL pointer dereference that can happen if the UDL
> driver is unloaded before the framebuffer is initialized. This can
> happen e.g. if the USB device is unplugged right after it was plugged
> in.
>
> As explained by Stéphane
On Fri, Sep 07, 2018 at 03:22:34PM +0800, Icenowy Zheng wrote:
> The R40 HDMI PHY seems to be different to the A64 one, the A64 one
> has no input mux, but the R40 one has.
>
> Drop the A64 fallback compatible from the HDMI PHY node in R40 DT.
>
> Signed-off-by: Icenowy Zheng
> ---
> arch/arm/b
On Fri, Sep 07, 2018 at 03:22:30PM +0800, Icenowy Zheng wrote:
> By experiments it seems that the A64 HDMI PHY is not able to use the
> second video PLL as the clock parent.
>
> Drop pll-1 from the device tree binding of A64 HDMI PHY.
>
> Signed-off-by: Icenowy Zheng
> ---
> Documentation/devic
On Fri, Sep 07, 2018 at 05:50:52PM +0300, Laurent Pinchart wrote:
> On Friday, 7 September 2018 11:56:23 EEST Maxime Ripard wrote:
> > On Wed, Sep 05, 2018 at 04:43:57PM +0300, Laurent Pinchart wrote:
> > >> The current set of parameters should cover all the potential users.
> > >>
> > >> Signed-o
Hi,
On Fri, Sep 07, 2018 at 05:26:29PM +0300, Laurent Pinchart wrote:
> > >> + */
> > >> +int phy_mipi_dphy_get_default_config(unsigned long pixel_clock,
> > >> + unsigned int bpp,
> > >> + unsigned int lanes,
> > >> +
On Fri, Aug 31, 2018 at 10:17:30AM +0200, Daniel Vetter wrote:
> On Thu, Aug 23, 2018 at 04:23:41PM +0100, Brian Starkey wrote:
> > Some formats have a non-integer number of bytes per pixel, which can't
> > be handled with the existing 'cpp' field in drm_format_info. To handle
> > these formats, ad
Hi,
Thanks for reporting this issue.
On 08/09/2018 18:48, MOHAMMAD RASIM wrote:
> Hi,
>
> I've an issue where the drm_meson driver doesn't work, it used to work in
> earlier 4.18 release and stopped working after about 4.18-rc3.
>
> My board is videostrong k2 pro (S905 SoC), I use the meson-gx
https://bugs.freedesktop.org/show_bug.cgi?id=107855
Pontus Gråskæg changed:
What|Removed |Added
CC||graaskaeg.via.forwarder@nev
https://bugzilla.kernel.org/show_bug.cgi?id=200695
Claude Heiland-Allen (cla...@mathr.co.uk) changed:
What|Removed |Added
Kernel Version|4.18.0-rc7, 4.18.5, 4.18.6, |4.18.0-rc7, 4.
Lots of code can be removed by relying on fb-helper:
- "struct drm_framebuffer" moves to fb_helper.fb.
- "struct drm_gem_object" moves to fb_helper.obj[0].
- "struct qxl_device" can be inferred as drm_fb_helper is embedded.
- qxl_user_framebuffer_create -> drm_gem_fb_create.
- qxl_user_framebuffer_
Am 10.09.2018 um 15:05 schrieb Tom St Denis:
On 2018-09-10 9:04 a.m., Christian König wrote:
Hi Tom,
I'm talking about adding new printks to figure out what the heck is
going wrong here.
Thanks,
Christian.
Hi Christian,
Sure, if you want to send me a simple patch that adds more printk I'l
On 2018-09-10 9:04 a.m., Christian König wrote:
Hi Tom,
I'm talking about adding new printks to figure out what the heck is
going wrong here.
Thanks,
Christian.
Hi Christian,
Sure, if you want to send me a simple patch that adds more printk I'll
gladly give it a try (doubly so since my wo
Hi Tom,
I'm talking about adding new printks to figure out what the heck is
going wrong here.
Thanks,
Christian.
Am 10.09.2018 um 14:59 schrieb Tom St Denis:
Hi Christian,
Are you adding new traces or turning on existing ones? Would you like
me to try them out in my setup?
Tom
On 2018-
Den 09.09.2018 16.13, skrev Laurent Pinchart:
Hi Noralf,
Thank you for the patch.
On Saturday, 8 September 2018 16:46:35 EEST Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbd
Den 10.09.2018 14.31, skrev Alexey Brodkin:
Hi Noralf,
On Sat, 2018-09-08 at 15:46 +0200, Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client
Hi Christian,
Are you adding new traces or turning on existing ones? Would you like
me to try them out in my setup?
Tom
On 2018-09-10 8:49 a.m., Christian König wrote:
Am 10.09.2018 um 14:05 schrieb Huang Rui:
On Mon, Sep 10, 2018 at 05:25:48PM +0800, Koenig, Christian wrote:
Am 10.09.201
Den 10.09.2018 09.28, skrev Maxime Ripard:
On Sat, Sep 08, 2018 at 03:46:43PM +0200, Noralf Trønnes wrote:
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callba
On 08/22/2018 10:54 AM, Daniel Vetter wrote:
> DRM drivers really, really, really don't want random userspace to
> share buffer behind it's back, bypassing the dma-buf buffer sharing
> machanism. For that reason we've ruthlessly rejected any IOCTL
> exposing the physical address of any graphics bu
Am 10.09.2018 um 14:05 schrieb Huang Rui:
On Mon, Sep 10, 2018 at 05:25:48PM +0800, Koenig, Christian wrote:
Am 10.09.2018 um 11:23 schrieb Huang Rui:
On Mon, Sep 10, 2018 at 11:00:04AM +0200, Christian König wrote:
Hi Ray,
well those patches doesn't make sense, the pointer is only local to
t
On 08/22/2018 10:54 AM, Daniel Vetter wrote:
> This was only added for the drm's fbdev emulation support, so that it
> would try harder to show the Oops.
>
> Unfortunately this never really worked reliably, and in practice ended
> up pushing the real Oops off the screen due to plentyfull locking,
https://bugs.freedesktop.org/show_bug.cgi?id=103300
--- Comment #3 from Ian Bruene ---
(In reply to Timothy Arceri from comment #2)
> Hi Ian,
>
> Is this still a problem with a recent version of Mesa?
Tested with a just updated ubuntu 18.04 + padoka unstable. The problem still
exists.
> If so
On 07/09/18 12:42, Maxime Ripard wrote:
> On Fri, Sep 07, 2018 at 01:26:30PM +0200, Arnd Bergmann wrote:
>> On Fri, Sep 7, 2018 at 11:41 AM Jon Hunter wrote:
>>>
>>>
>>> On 11/07/18 15:43, Arnd Bergmann wrote:
Having DRM_SUN4I built-in but DRM_SUN8I_MIXER as a loadable module results
i
On Sun, Sep 09, 2018 at 02:03:57PM +0200, Daniel Vetter wrote:
> On Sat, Sep 08, 2018 at 03:58:53PM +0200, Neil Armstrong wrote:
> > Hi Ayan,
> >
> > On 10/07/2018 15:18, Ayan Kumar Halder wrote:
> > > In the current series of patches, we are trying to add support for AFBC
> > > modifiers in malid
Hello,
On Monday, 10 September 2018 14:59:23 EEST Tomi Valkeinen wrote:
> Hi Pavel,
>
> (dropping Dave, no need to spam him)
>
> On 30/08/18 12:04, Pavel Machek wrote:
> > Hi!
> >
> > There's neat series of patches on
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.gi
Hi Gerd,
Thank you for the patch.
CC'ing the linux-api mailing list as this creates a new userspace API.
On Monday, 27 August 2018 12:34:44 EEST Gerd Hoffmann wrote:
> A driver to let userspace turn memfd regions into dma-bufs.
>
> Use case: Allows qemu create dmabufs for the vga framebuffer o
On Mon, Sep 10, 2018 at 05:25:48PM +0800, Koenig, Christian wrote:
> Am 10.09.2018 um 11:23 schrieb Huang Rui:
> > On Mon, Sep 10, 2018 at 11:00:04AM +0200, Christian König wrote:
> >> Hi Ray,
> >>
> >> well those patches doesn't make sense, the pointer is only local to
> >> the function.
> > You'r
On Fri, Sep 07, 2018 at 02:46:21PM -0700, Satish Kumar Nagireddy wrote:
> The requirement is to render interlaced alternate buffers. In case of
> alternate, top field and bottom field are in two different buffers.
>
> The question is, can we pass existing flags DRM_MODE_PRESENT_TOP_FIELD
> and DRM
Hi Pavel,
(dropping Dave, no need to spam him)
On 30/08/18 12:04, Pavel Machek wrote:
> Hi!
>
> There's neat series of patches on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/?h=droid4-pending-v4.19
>
> They enable display support for my hardware. As you can im
On Mon, Sep 10, 2018 at 05:25:48PM +0800, Koenig, Christian wrote:
> Am 10.09.2018 um 11:23 schrieb Huang Rui:
> > On Mon, Sep 10, 2018 at 11:00:04AM +0200, Christian König wrote:
> >> Hi Ray,
> >>
> >> well those patches doesn't make sense, the pointer is only local to
> >> the function.
> > You'r
On Mon, 10 Sep 2018, "Lee, Shawn C" wrote:
> The N value was computed by kernel driver that based on synchronous clock
> mode. But only specific N value (0x8000) would be acceptable for
> LG LP140WF6-SPM1 eDP panel which is running at asynchronous clock mode.
> With the other N value, Tcon will en
On Mon, 10 Sep 2018, "Lee, Shawn C" wrote:
> Some DP dongles in particular seem to be fussy about too large
> link M/N values. Set specific value for N divider can resolve
> this issue per dongle vendor's comment. So configure N as
> constant value (0x8000) to instead of reduce M/N formula when
>
On Mon, 10 Sep 2018, "Lee, Shawn C" wrote:
> DP quirk list just compare sink or branch device's OUI so far.
> That means particular vendor's products will be applied specific
> change. This change would confirm device_id the same or not.
> Then driver can implement some changes for branch/sink dev
https://bugs.freedesktop.org/show_bug.cgi?id=107880
Marvin Damschen changed:
What|Removed |Added
Attachment #141500|0 |1
is obsolete|
Add gamma_lut/degamma_lut/ctm checking before pushing
staged color management properties on the CRTC.
If above object is NULL, return directly.
Signed-off-by: Aaron Liu
---
src/drmmode_display.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/src/drmmode_display.c b/src/drmm
https://bugs.freedesktop.org/show_bug.cgi?id=107880
--- Comment #5 from Marvin Damschen ---
(In reply to Michel Dänzer from comment #4)
> Looks like there may be an issue with the VCN microcode loading. Does
>
> amdgpu.ip_block_mask=0xff
>
> on the kernel command line avoid the problem?
It doe
https://bugs.freedesktop.org/show_bug.cgi?id=107595
Pontus Gråskæg changed:
What|Removed |Added
CC||graaskaeg.via.forwarder@nev
https://bugs.freedesktop.org/show_bug.cgi?id=107880
--- Comment #4 from Michel Dänzer ---
Looks like there may be an issue with the VCN microcode loading. Does
amdgpu.ip_block_mask=0xff
on the kernel command line avoid the problem?
Can you bisect?
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=107880
--- Comment #3 from Marvin Damschen ---
Created attachment 141502
--> https://bugs.freedesktop.org/attachment.cgi?id=141502&action=edit
Modprobe amdgpu freezes video output with 4.19-rc3
--
You are receiving this mail because:
You are the as
https://bugs.freedesktop.org/show_bug.cgi?id=107880
--- Comment #2 from Marvin Damschen ---
(In reply to Michel Dänzer from comment #1)
> (In reply to Marvin Damschen from comment #0)
> > System hangs after "fb: switching to amdgpudrmfb from EFI VGA".
>
> How long have you waited for? E.g. if a
https://bugs.freedesktop.org/show_bug.cgi?id=107855
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=107855
--- Comment #9 from Pontus Gråskæg ---
Just to be clear, booting with kernel 4.19rc2 does indeed remove the "*ERROR*
VCE not responding, giving up!!!" and associated messages. So that can be
marked solved (I think).
However, there is still a reg
On Mon, Sep 10, 2018 at 1:11 PM Jyri Sarha wrote:
>
> On 10/09/18 09:45, Souptick Joarder wrote:
> > On Wed, Aug 8, 2018 at 9:43 PM Souptick Joarder
> > wrote:
> >>
> >> convert drm_atomic_helper_suspend/resume() to use
> >> drm_mode_config_helper_suspend/resume().
> >>
> >> saved_state in tilcd
https://bugs.freedesktop.org/show_bug.cgi?id=107863
Michel Dänzer changed:
What|Removed |Added
Attachment #141478|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=107858
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com,
https://bugs.freedesktop.org/show_bug.cgi?id=107876
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
1 - 100 of 160 matches
Mail list logo
