In HDMI 1.4 defines 4k modes without specific aspect ratio.
However, in HDMI 2.0, adds aspect ratio attribute to distinguish different
4k modes.
According to Appendix E of HDMI 2.0 spec, source should use VSIF to
indicate VIC mode only when the mode is one defined in HDMI 1.4b 4K modes.
On Mon, Sep 23, 2019 at 12:16:12PM +, Brian Starkey wrote:
> Hi Lowry,
>
> On Fri, Sep 20, 2019 at 09:43:47AM +, Lowry Li (Arm Technology China)
> wrote:
> > From: "Lowry Li (Arm Technology China)"
> >
> > Sets color_depth according to connector->bpc.
> > Adds a new optional DT
On 9/23/19 2:02 AM, Brendan Higgins wrote:
> diff --git a/Documentation/dev-tools/kunit/usage.rst
> b/Documentation/dev-tools/kunit/usage.rst
> new file mode 100644
> index ..c6e69634e274
> --- /dev/null
> +++ b/Documentation/dev-tools/kunit/usage.rst
> @@ -0,0 +1,576 @@
> +..
> -Original Message-
> From: Jason Wang
> Sent: Monday, September 23, 2019 8:03 AM
> To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org; intel-gvt-...@lists.freedesktop.org;
>
I tired to run some tests on 5.4 and I was getting errors. I went all
the way back to 5.0 and I get errors. 4.19 seems to work just fine.
I was curious to know if anyone is seeing errors. I'll bisect
tomorrow, but I thought I'd ask before I got too far.
# LIBGL_DEBUG=verbose glmark2-es2-drm
> -Original Message-
> From: Jason Wang
> Sent: Monday, September 23, 2019 8:03 AM
> To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org; intel-gvt-...@lists.freedesktop.org;
>
Hi John,
I didn't see any response about using the test harness. Did you decide
against it?
On Fri, Sep 06, 2019 at 06:47:12PM +, John Stultz wrote:
> Add very trivial allocation and import test for dma-heaps,
> utilizing the vgem driver as a test importer.
>
> A good chunk of this code
Hi John,
I spotted one thing below which might be harmless, but best to check.
On Fri, Sep 06, 2019 at 06:47:11PM +, John Stultz wrote:
> This adds a CMA heap, which allows userspace to allocate
> a dma-buf of contiguous memory out of a CMA region.
>
> This code is an evolution of the
On Fri, Sep 06, 2019 at 06:47:10PM +, John Stultz wrote:
> This patch adds system heap to the dma-buf heaps framework.
>
> This allows applications to get a page-allocator backed dma-buf
> for non-contiguous memory.
>
> This code is an evolution of the Android ION implementation, so
> thanks
Hi John,
On Fri, Sep 06, 2019 at 06:47:08PM +, John Stultz wrote:
> From: "Andrew F. Davis"
>
> This framework allows a unified userspace interface for dma-buf
> exporters, allowing userland to allocate specific types of memory
> for use in dma-buf sharing.
>
> Each heap is given its own
Hi John,
On Fri, Sep 06, 2019 at 06:47:09PM +, John Stultz wrote:
> Add generic helper dmabuf ops for dma heaps, so we can reduce
> the amount of duplicative code for the exported dmabufs.
>
> This code is an evolution of the Android ION implementation, so
> thanks to its original authors
https://bugs.freedesktop.org/show_bug.cgi?id=111761
Christian Zigotzky changed:
What|Removed |Added
Attachment #145482|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=111761
--- Comment #3 from Christian Zigotzky ---
Created attachment 145482
--> https://bugs.freedesktop.org/attachment.cgi?id=145482=edit
DRM patch
--
You are receiving this mail because:
You are the assignee for the
On 9/23/19 2:18 PM, shuah wrote:
> I would like to apply the series very soon so it gets some soak time
> after this move in linux-next and it can still make the rc1.
>
> Since there changes can be addressed after rc1, I would like to not
> require Brendan to do another version before I apply.
>
On 9/23/19 1:49 PM, Randy Dunlap wrote:
On 9/23/19 11:06 AM, Brendan Higgins wrote:
On Mon, Sep 23, 2019 at 8:48 AM Randy Dunlap wrote:
On 9/23/19 2:02 AM, Brendan Higgins wrote:
Add documentation for KUnit, the Linux kernel unit testing framework.
- Add intro and usage guide for KUnit
-
https://bugs.freedesktop.org/show_bug.cgi?id=111792
--- Comment #2 from Sylvain BERTRAND ---
Created attachment 145481
--> https://bugs.freedesktop.org/attachment.cgi?id=145481=edit
xorg
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111792
--- Comment #1 from Sylvain BERTRAND ---
Created attachment 145480
--> https://bugs.freedesktop.org/attachment.cgi?id=145480=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111792
Bug ID: 111792
Summary: [AMD tahiti xt] amd-staging-drm-next broken since
linux 5.3.0-rc3 rebase
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
Hi Jason,
> -Original Message-
> From: Jason Wang
> Sent: Monday, September 23, 2019 8:03 AM
> To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org;
Hi Jason,
> -Original Message-
> From: Jason Wang
> Sent: Monday, September 23, 2019 8:03 AM
> To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org; intel-gvt-...@lists.freedesktop.org;
https://bugs.freedesktop.org/show_bug.cgi?id=110457
--- Comment #13 from darkshvein ---
Hello.
please, explain.
Why I work fine with FX-8320 CPU,
but after Ryzen r5 1600 upgrade, I see this OS freezes and bug?
is pcie generation any cause? planned obsolescence?
or coincidence with amdgpu
https://bugs.freedesktop.org/show_bug.cgi?id=111791
Bug ID: 111791
Summary: mesa-19.2-rc4: Fails to execute OpenCL kernel (ac_rtld
error: !s->is_rx) on AMD64 and armhf at least
Product: Mesa
Version: 19.2
Hardware: All
On 9/23/19 11:06 AM, Brendan Higgins wrote:
> On Mon, Sep 23, 2019 at 8:48 AM Randy Dunlap wrote:
>>
>> On 9/23/19 2:02 AM, Brendan Higgins wrote:
>>> Add documentation for KUnit, the Linux kernel unit testing framework.
>>> - Add intro and usage guide for KUnit
>>> - Add API reference
>>>
>>>
https://bugs.freedesktop.org/show_bug.cgi?id=111761
--- Comment #2 from Christian Zigotzky ---
The changes of the following files are responsible for the boot issue.
- drivers/gpu/drm/drm_*
- include/drm/*
The kernel doesn't boot with the updates in the files above from the
On Mon, Sep 23, 2019 at 06:05:22AM -0700, sandy.huang wrote:
>
> 在 2019/9/23 上午5:53, Ville Syrjälä 写道:
> > On Mon, Sep 23, 2019 at 08:38:50PM +0800, Sandy Huang wrote:
> >> diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h
> >> index 3feeaa3..5fe89e9 100644
> >> ---
On Mon, Sep 23, 2019 at 10:27 AM AngeloGioacchino Del Regno
wrote:
>
> Il giorno lun 23 set 2019 alle ore 18:37 Rob Clark
> ha scritto:
> >
> > On Sat, Sep 21, 2019 at 3:04 AM wrote:
> > >
> > > From: "Angelo G. Del Regno"
> > >
> > > The Adreno 510 GPU is a stripped version of the Adreno 5xx,
https://bugs.freedesktop.org/show_bug.cgi?id=111789
Bug ID: 111789
Summary: drm/etnaviv: command buffer outside valid memory
window (on cubox i4), Linux 5.3
Product: DRI
Version: unspecified
Hardware: ARM
On Mon, Sep 23, 2019 at 8:48 AM Randy Dunlap wrote:
>
> On 9/23/19 2:02 AM, Brendan Higgins wrote:
> > Add documentation for KUnit, the Linux kernel unit testing framework.
> > - Add intro and usage guide for KUnit
> > - Add API reference
> >
> > Signed-off-by: Felix Guo
> > Signed-off-by:
Hi,
thanks a lot for the review, Andrzej!
Andrzej Hajda:
>> +static const struct backlight_ops s6e8aa0_backlight_ops = {
>> +.update_status = s6e8aa0_set_brightness,
>
>
> This is racy, update_status can be called in any time between probe and
> remove, particularly:
>
> a) before panel
https://bugs.freedesktop.org/show_bug.cgi?id=22
--- Comment #30 from William Bonnaventure ---
Fixed issue with a BIOS update on Lenovo E485 (v1.54 with AMD 2500U) with
Fedora 30 KDE.
I had an issue on previous BIOS that requires a kernel option to boot on all
kernels
Hi Sandy.
Thanks for taking care of this, but...
On Mon, Sep 23, 2019 at 08:51:45PM +0800, Sandy Huang wrote:
> cpp[BytePerPlane] can't describe the 10bit data format correctly,
> So we use bpp[BitPerPlane] to instead cpp.
>
> Signed-off-by: Sandy Huang
> ---
>
Separating the management of buffer objects from updating the hardware
cursor buffer gives the code more structure. While doing this, we can
further split the image-update code into code for writing the buffer,
setting the base scan-out address, and enabling the cursor. The first
two operations
By putting cursor BOs at the high end of the video memory, we can avoid
memory fragmentation. Starting at the low end, contiguous video memory is
available for framebuffers.
The patch also simplifies the buffer swapping by splitting
struct ast_private.cursor_cache BO into two separate boffer
By putting cursor BOs at the high end of the video memory, we can avoid
memory fragmentation. Starting at the low end, contiguous video memory is
available for framebuffers.
The patch also simplifies the buffer swapping and aligns it with the
ast driver. If there are more drivers with similar
Although the driver source code is fairly inconsistent wrt naming, the
prefix should be mgag200. Rename cursor functions accordingly.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/mgag200/mgag200_cursor.c | 19 ---
drivers/gpu/drm/mgag200/mgag200_drv.h| 6 +++---
Selecting the correct BO for the new cursor image is not relevant
outside of mgag200_show_cursor(). Let the function do the work.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/mgag200/mgag200_cursor.c | 120 +++
1 file changed, 56 insertions(+), 64 deletions(-)
diff
(was: drm/vram: Add VRAM buffers for HW cursors)
This patchset cleans up the memory management of HW cursors in ast and
mgag200. It further moves the allocated cursor BOs to the of the video
RAM to reduce memory fragmentation.
The ast and mgag200 drivers support HW cursors of uncommon pixel
The double-buffered cursor image is currently stored in video memory
by creating two BOs and pinning them to VRAM. The exact location is
chosen by VRAM helpers. The pinned cursor BOs can conflict with
framebuffer BOs and prevent the primary plane from displaying its
framebuffer.
As a first step
Selecting the correct offset for the new cursor image is not relevant
outside of ast_show_cursor(). Let the function do the work.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_mode.c | 57 ++
1 file changed, 31 insertions(+), 26 deletions(-)
diff
Separating the cursor's move() function from the show() function in
preparation of further rework of the cursor update code.
'Showing' the cursor from within the move() function is required to
update the cursor position.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_mode.c | 5
Moving the cursor initialization and cleanup into separate functions
makes the overall code slightly more readable.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/mgag200/mgag200_cursor.c | 28
drivers/gpu/drm/mgag200/mgag200_drv.h| 2 ++
Adding mgag200_move_cursor() makes the cursor code more consistent and
will become handy when we move to universal cursor planes.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/mgag200/mgag200_cursor.c | 29
1 file changed, 20 insertions(+), 9 deletions(-)
diff
Pinning lots of small buffer objects, such as cursors or sprites, to video
memory can lead to fragmentation, which is a problem for devices with only
a small amount of memory. As a result, framebuffer images might not get
pinned, even though there's enough space available overall.
The flag
A call to ast's show-cursor function now receives the cursor image
and updates the buffer. The change splits off image update and
base-address update into separate functions.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_mode.c | 120 +++--
1 file
There is no point to print deferred probe (and its failures to get
resources) as an error. Also there is no need to print regulator errors
twice.
In case of multiple probe tries this would pollute the dmesg.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. Remove second error
On Mon, Sep 23, 2019 at 5:44 AM Sandy Huang wrote:
>
> cpp[BytePerPlane] can't describe the 10bit data format correctly,
> So we use bpp[BitPerPlane] to instead cpp.
>
> Signed-off-by: Sandy Huang
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 4 ++--
>
On Thu, Sep 12, 2019 at 10:36:25AM +0100, Steven Price wrote:
> On 09/09/2019 16:51, Krzysztof Kozlowski wrote:
> > There is no point to print deferred probe (and its failures to get
> > resources) as an error.
> >
> > In case of multiple probe tries this would pollute the dmesg.
> >
> >
On Sat, Sep 21, 2019 at 3:04 AM wrote:
>
> From: "Angelo G. Del Regno"
>
> The Adreno 510 GPU is a stripped version of the Adreno 5xx,
> found in low-end SoCs like 8x56 and 8x76, which has 256K of
> GMEM, with no GPMU nor ZAP.
> Also, since the Adreno 5xx part of this driver seems to be
>
the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Laurentiu-Palcu/Add-support-for-iMX8MQ-Display-Controller-Subsystem/20190923-230115
config: c6x-allyesconfig (attached as .config)
compiler: c6x-elf-gcc (GCC) 7.4.0
Hi Daniel, Dave,
Here is a new round of drm-misc-next fixes
Maxime
drm-misc-next-fixes-2019-09-23:
- Multiple panfrost fixes for regulator support and page fault handling
- Some cleanups and fixes in the self-refresh helpers
- Some cleanups and fixes in the atomic helpers
The following
On Mon, 23 Sep 2019 21:03:26 +0800
Jason Wang wrote:
> Mdev bus only supports vfio driver right now, so it doesn't implement
> match method. But in the future, we may add drivers other than vfio,
> one example is virtio-mdev[1] driver. This means we need to add device
> class id support in bus
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #144 from sehell...@gmail.com ---
I also think this is strange. Since yesterday, they turned off and on many
times successfully without any problems. Most likely, it's connected with
something else, but I don’t know where to find.
Adjust indentation from spaces to tab (+optional two spaces) as in
coding style with command like:
$ sed -e 's/^/\t/' -i */Kconfig
Signed-off-by: Krzysztof Kozlowski
---
arch/Kconfig | 4 ++--
arch/alpha/Kconfig | 2 +-
Hi Heikki,
On Mon, Sep 23, 2019 at 06:03:33PM +0300, Heikki Krogerus wrote:
> On Sat, Sep 21, 2019 at 02:12:28AM +0300, Laurent Pinchart wrote:
> > Hi Dmitry,
> >
> > (CC'ing Heikki as the original author of software nodes support)
> >
> > Thank you for the patch.
> >
> > On Wed, Sep 11, 2019
On Mon, Sep 23, 2019 at 09:45:59AM -0600, Alex Williamson wrote:
> On Mon, 23 Sep 2019 21:03:30 +0800
> Jason Wang wrote:
>
> > We want to copy from iov to buf, so the direction was wrong.
> >
> > Signed-off-by: Jason Wang
> > ---
> > drivers/vhost/vringh.c | 8 +++-
> > 1 file changed, 7
Adjust indentation from spaces to tab (+optional two spaces) as in
coding style with command like:
$ sed -e 's/^/\t/' -i */Kconfig
Signed-off-by: Krzysztof Kozlowski
---
certs/Kconfig | 14 ++---
init/Kconfig | 28 +-
Adjust indentation from spaces to tab (+optional two spaces) as in
coding style with command like:
$ sed -e 's/^/\t/' -i */Kconfig
Signed-off-by: Krzysztof Kozlowski
---
drivers/gpu/drm/Kconfig | 10 +-
drivers/gpu/drm/amd/display/Kconfig | 20 ++--
On Sat, Sep 21, 2019 at 12:04:39PM +0200, khol...@gmail.com wrote:
> From: "Angelo G. Del Regno"
>
> The Adreno 510 GPU is a stripped version of the Adreno 5xx,
> found in low-end SoCs like 8x56 and 8x76, which has 256K of
> GMEM, with no GPMU nor ZAP.
> Also, since the Adreno 5xx part of this
On 9/23/19 2:02 AM, Brendan Higgins wrote:
> Add documentation for KUnit, the Linux kernel unit testing framework.
> - Add intro and usage guide for KUnit
> - Add API reference
>
> Signed-off-by: Felix Guo
> Signed-off-by: Brendan Higgins
> Cc: Jonathan Corbet
> Reviewed-by: Greg Kroah-Hartman
On Mon, 23 Sep 2019 21:03:30 +0800
Jason Wang wrote:
> We want to copy from iov to buf, so the direction was wrong.
>
> Signed-off-by: Jason Wang
> ---
> drivers/vhost/vringh.c | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Why is this included in the series? Seems like an
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #143 from Tom B ---
I'm not sure how KDE handles monitor power behind the scenes but I have an
uptime of 2 days now since applying the patches and with KDE I've let it turn
off the monitors at least 6 or 7 times and suspend/resume 3
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #142 from sehell...@gmail.com ---
(In reply to Alex Deucher from comment #141)
> (In reply to sehellion from comment #140)
> > Created attachment 145463 [details]
> > 5.3.1 with Alex's patches and dual monitors, crash
>
> That's not
rop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see
> https://stackoverflow.com/a/37406982]
>
> url:
> https://github.com/0day-ci/linux/commits/Jason-Wang/mdev-based-hardware-virtio-offl
Quoting Brendan Higgins (2019-09-23 02:02:36)
> KUnit is a new unit testing framework for the kernel and when used is
> built into the kernel as a part of it. Add KUnit to the lib Kconfig and
> Makefile to allow it to be actually built.
>
> Signed-off-by: Brendan Higgins
> Cc: Randy Dunlap
>
Dear All,
As a result of my mistake I've sent this patch with an incorrect SOB chain.
Please kindly disregard this patch.
@Neil: thank you for your time you spent reviewing it and answering and I'm
sorry it's to no effect.
@Ezequiel, @Tomeu: I apologize to you. My mistake.
Regards,
Hi,
On Fri 13 Sep 19, 20:16, Rob Herring wrote:
> On Fri, Sep 13, 2019 at 4:58 PM Paul Kocialkowski
> wrote:
> >
> > Hi Rob and thanks for the review!
> >
> > On Fri 13 Sep 19, 15:35, Rob Herring wrote:
> > > On Tue, Sep 10, 2019 at 05:34:08PM +0200, Paul Kocialkowski wrote:
> > > > The Xylon
https://bugs.freedesktop.org/show_bug.cgi?id=111784
Emmanuel Durand changed:
What|Removed |Added
Version|XOrg git|DRI git
--
You are receiving this
On Fri, Sep 20, 2019 at 10:12:30PM +0200, Jernej Škrabec wrote:
> Dne petek, 20. september 2019 ob 08:08:20 CEST je Maxime Ripard napisal(a):
> > Hi
> >
> > On Thu, Sep 19, 2019 at 09:39:19PM +0200, Daniel Vetter wrote:
> > > On Thu, Sep 19, 2019 at 7:30 PM Maxime Ripard wrote:
> > > > The newer
On Thu, Sep 19, 2019 at 08:24:18PM +0200, Jernej Škrabec wrote:
> Dne četrtek, 19. september 2019 ob 19:30:20 CEST je Maxime Ripard napisal(a):
> > The newer Allwinner SoCs have a different layers controller than the older
> > ones. Jernej wrote that support and has been reviewing patches for a
On Mon, Sep 23, 2019 at 11:03:35AM -0400, Tony Camuso wrote:
> On 7/12/19 1:06 PM, Ville Syrjälä wrote:
> > On Fri, Jul 12, 2019 at 12:07:46PM -0400, Tony Camuso wrote:
> >> On 7/10/19 9:56 AM, Ville Syrjälä wrote:
> >>> On Wed, Jul 10, 2019 at 09:47:11AM -0400, Tony Camuso wrote:
> On
tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Jason-Wang/mdev-based-hardware-virtio-offloading-support/20190923-210738
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 7.4.0
reproduce
On Mon, Sep 23, 2019 at 8:56 AM Sandy Huang wrote:
>
> cpp[BytePerPlane] can't describe the 10bit data format correctly,
> So we use bpp[BitPerPlane] to instead cpp.
>
> Signed-off-by: Sandy Huang
> ---
> drivers/gpu/drm/nouveau/dispnv04/crtc.c | 7 ---
>
On 7/12/19 1:06 PM, Ville Syrjälä wrote:
On Fri, Jul 12, 2019 at 12:07:46PM -0400, Tony Camuso wrote:
On 7/10/19 9:56 AM, Ville Syrjälä wrote:
On Wed, Jul 10, 2019 at 09:47:11AM -0400, Tony Camuso wrote:
On 5/24/19 4:36 AM, Jani Nikula wrote:
On Thu, 23 May 2019, tcamuso wrote:
From
On Sat, Sep 21, 2019 at 02:12:28AM +0300, Laurent Pinchart wrote:
> Hi Dmitry,
>
> (CC'ing Heikki as the original author of software nodes support)
>
> Thank you for the patch.
>
> On Wed, Sep 11, 2019 at 12:52:10AM -0700, Dmitry Torokhov wrote:
> > Instead of fwnode_get_named_gpiod() that I
https://bugs.freedesktop.org/show_bug.cgi?id=111761
--- Comment #1 from Alex Deucher ---
Can you bisect? Please attach your xorg log and dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
On Mon, Sep 23, 2019 at 04:52:50PM +0300, Jani Nikula wrote:
> On Fri, 20 Sep 2019, Thierry Reding wrote:
> > On Mon, Sep 02, 2019 at 01:31:00PM +0200, Thierry Reding wrote:
> >> From: Thierry Reding
> >>
> >> Hi,
> >>
> >> this series of patches improves the DP helpers a bit and cleans up
https://bugs.freedesktop.org/show_bug.cgi?id=111785
Andre Klapper changed:
What|Removed |Added
Component|General |Two
Group|
https://bugs.freedesktop.org/show_bug.cgi?id=111784
Emmanuel Durand changed:
What|Removed |Added
Priority|not set |high
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=111785
Bug ID: 111785
Summary: Registration not working
Product: DRI
Version: DRI git
Hardware: Other
URL: http://localhost:4000
OS: Windows (All)
Status:
https://bugs.freedesktop.org/show_bug.cgi?id=111784
--- Comment #2 from Emmanuel Durand ---
Created attachment 145474
--> https://bugs.freedesktop.org/attachment.cgi?id=145474=edit
Source code exhibiting the issue
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111784
--- Comment #1 from Emmanuel Durand ---
Created attachment 145473
--> https://bugs.freedesktop.org/attachment.cgi?id=145473=edit
Xorg log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111784
Bug ID: 111784
Summary: Hang when using glWaitSync with multithreaded shared
GL contexts
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #141 from Alex Deucher ---
(In reply to sehellion from comment #140)
> Created attachment 145463 [details]
> 5.3.1 with Alex's patches and dual monitors, crash
That's not a crash, it's just a warning.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=110674
Alex Deucher changed:
What|Removed |Added
Attachment #145463|text/x-log |text/plain
mime type|
Add bindings for iMX8MQ Display Controller Subsystem.
Signed-off-by: Laurentiu Palcu
---
.../bindings/display/imx/nxp,imx8mq-dcss.yaml | 86 ++
1 file changed, 86 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/imx/nxp,imx8mq-dcss.yaml
diff
Hi,
This patchset adds initial DCSS support for iMX8MQ chip. Initial support
includes only graphics plane support (no video planes), no HDR10 capabilities,
no graphics decompression (only linear, tiled and super-tiled buffers allowed).
Support for the rest of the features will be added
Currently the drm/imx/ directory is compiled only if DRM_IMX is set. Adding a
new IMX related IP in the same directory would need DRM_IMX to be set, which
would
bring in also IPUv3 core driver...
The current patch would allow adding new IPs in the imx/ directory without
needing
to set DRM_IMX.
On Mon, 23 Sep 2019 at 14:06, Daniel Vetter wrote:
>
> On Sat, Sep 21, 2019 at 10:33 AM Heinrich Fink
> wrote:
> >
> > On Tue, 3 Sep 2019 at 11:53, Daniel Vetter wrote:
> > >
> > > On Tue, Sep 03, 2019 at 11:19:19AM +0200, Heinrich Fink wrote:
> > > > On Tue, 3 Sep 2019 at 09:46, Daniel Vetter
On Mon, Sep 23, 2019 at 08:59:46AM +0200, Gerd Hoffmann wrote:
> On Fri, Sep 20, 2019 at 03:35:52PM -0400, Sean Paul wrote:
> > From: Sean Paul
> >
> > Fixes
> > include/drm/drm_gem_ttm_helper.h:1: warning: no structured comments found
>
> Reviewed-by: Gerd Hoffmann
>
Thanks, pushed to
I wish you would think more about the error codes that you're returning.
Most functions do "ret |= frob()." which ORs the error codes together,
and results in a nonsense negative error code. But then some functions
return 1 on error and zero on success which is sometimes a bug,
sometimes
On Mon, Sep 23, 2019 at 09:03:25PM +0800, Jason Wang wrote:
> Hi all:
>
> There are hardware that can do virtio datapath offloading while having
> its own control path. This path tries to implement a mdev based
> unified API to support using kernel virtio driver to drive those
> devices. This is
https://bugzilla.kernel.org/show_bug.cgi?id=204965
Bug ID: 204965
Summary: [amdgpu]] *ERROR* ring gfx test failed (-110) upon
wake from sleep, no video or frozen video
Product: Drivers
Version: 2.5
Kernel Version:
On 23/09/2019 14:20, Andrzej Pietrasiewicz wrote:
> From: Ezequiel Garcia
>
> AFBC is a proprietary lossless image compression protocol and format.
> It helps reduce memory bandwidth of the graphics pipeline operations.
> This, in turn, improves power efficiency.
>
> Signed-off-by: Ezequiel
On Fri, 20 Sep 2019, Thierry Reding wrote:
> On Mon, Sep 02, 2019 at 01:31:00PM +0200, Thierry Reding wrote:
>> From: Thierry Reding
>>
>> Hi,
>>
>> this series of patches improves the DP helpers a bit and cleans up some
>> inconsistencies along the way.
>>
>> v2 incorporates all review
On Mon, Sep 23, 2019 at 08:46:23PM +0800, Sandy Huang wrote:
> cpp[BytePerPlane] can't describe the 10bit data format correctly,
> So we use bpp[BitPerPlane] to instead cpp.
>
> Signed-off-by: Sandy Huang
Adding Ayan as well.
Best regards,
Liviu
> ---
>
With the removal of the panel-dpi from the omap drivers, the
LCD no longer works. This patch points the device tree to
a newly created panel named "logicpd,type28"
Fixes: 8bf4b1621178 ("drm/omap: Remove panel-dpi driver")
Signed-off-by: Adam Ford
Acked-by: Sam Ravnborg
---
V2: Remove legacy
This patch adds documentation of device tree bindings for the WVGA panel
Logic PD Type 28 display.
Signed-off-by: Adam Ford
---
V2: Use YAML instead of TXT for binding
diff --git
a/Documentation/devicetree/bindings/display/panel/logicpd,type28.yaml
Previously, there was an omap panel-dpi driver that would
read generic timings from the device tree and set the display
timing accordingly. This driver was removed so the screen
no longer functions. This patch modifies the panel-simple
file to setup the timings to the same values previously
On 17/09/2019 08:15, Boris Brezillon wrote:
> On Mon, 16 Sep 2019 17:20:28 -0500
> Rob Herring wrote:
>
>> On Fri, Sep 13, 2019 at 6:17 AM Boris Brezillon
>> wrote:
>>>
>>> The READ/WRITE flags are particularly useful if we want to avoid
>>> serialization of jobs that read from the same BO but
On Mon, Sep 23, 2019 at 08:58:14AM +0200, Gerd Hoffmann wrote:
> There is little reason for the from/to logic, printing a subset of
> the bits can be done by simply shifting/masking value if needed.
>
> Also use for_each_set_bit().
>
> Suggested-by: Jani Nikula
> Signed-off-by: Gerd Hoffmann
>
1 - 100 of 224 matches
Mail list logo
