https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #11 from Tapani Pälli ---
(In reply to Yunchao He from comment #10)
> (In reply to Tapani Pälli from comment #8)
> > What comes to conformance, you should refer to latest OpenGL spec (now being
> > 4.6). In this
https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #10 from Yunchao He ---
(In reply to Tapani Pälli from comment #8)
> What comes to conformance, you should refer to latest OpenGL spec (now being
> 4.6). In this case you want to render to RGB32F we should take
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #4 from Levis Raju ---
amdgpu :38:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:1
pasid:32768)
amdgpu :38:00.0: at page 0x00010760d000 from 27
amdgpu :38:00.0:
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #16 from Alex Deucher ---
vega10 does not support VP9.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
Hi Jani,
Good day!
Thank you for taking the time to point out those information. It’s a great help
to me.
Also apologies for the late reply, your first reply went to my spam inbox, not
sure what happen and I was waiting for replies for days.
I'm still new to Linux and to DRM. I also need to
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #15 from mikhail.v.gavri...@gmail.com ---
> Maybe try different combination of mpv parameters. E.g. explicitly specify
> which hw decoding and which output driver to use.
I added output parameter but nothing is changed. Hardware
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #14 from mikhail.v.gavri...@gmail.com ---
Created attachment 139727
--> https://bugs.freedesktop.org/attachment.cgi?id=139727=edit
mpv h264
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #13 from mikhail.v.gavri...@gmail.com ---
Created attachment 139726
--> https://bugs.freedesktop.org/attachment.cgi?id=139726=edit
mpv vp9
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #9 from Ilia Mirkin ---
"Color-renderable" means "is it legal to use this format". It does NOT mean
"the driver allows rendering to this format".
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=104063
--- Comment #3 from lumiseven ---
Got the same error after upgrade my system and would you mind tell us how to
fix this issue in your case?
--
You are receiving this mail because:
You are the assignee for the
On Thu, May 24, 2018 at 1:04 AM, Rob Herring wrote:
> On Fri, May 18, 2018 at 05:27:53PM +0800, Qiang Yu wrote:
>> Signed-off-by: Qiang Yu
>> ---
>> Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt | 4
>> 1 file changed, 4 insertions(+)
>>
>>
https://bugs.freedesktop.org/show_bug.cgi?id=106601
wangjingbin changed:
What|Removed |Added
Summary|The internal format RGB32F |The internal
Add support for Truly NT35597 panel used
in MSM reference platforms.
This panel supports both single DSI and dual DSI
modes.
However, this patch series adds support only for
dual DSI mode.
Changes in v3:
- Changes to commit text
- Separated the documentation from the driver itself
- Improved
Add the device tree bindings for Truly NT35597 panel.
This panel supports both single DSI and dual DSI.
However, this patch series supports only dual DSI.
Signed-off-by: Abhinav Kumar
---
.../devicetree/bindings/display/truly,nt35597.txt | 69 ++
1
Add the device tree bindings for Truly NT35597 panel.
This panel supports both single DSI and dual DSI.
However, this patch series supports only dual DSI.
Signed-off-by: Abhinav Kumar
---
.../devicetree/bindings/display/truly,nt35597.txt | 69 ++
1
This panel supports both single DSI and dual DSI
modes.
However, this patch series adds support only for
dual DSI mode.
Changes in v3:
- Changes to commit text
- Separated the documentation from the driver itself
- Improved the documentation to cover the port information
- Formatting fixes and
On Wed, May 23, 2018 at 9:41 PM, Christian König
wrote:
> Am 23.05.2018 um 15:13 schrieb Qiang Yu:
>>
>> On Wed, May 23, 2018 at 5:35 PM, Christian König
>> wrote:
>>>
>>> Well NAK, that brings back a callback we worked quite hard on
Hi Bjorn
Thanks for the comments.
I will upload a new patch for this which will be dependent on
https://patchwork.kernel.org/patch/10377537/ series.
This series registers the backlight device we need.
Thanks
Abhinav
On 2018-04-18 21:42, Bjorn Andersson wrote:
On Wed 18 Apr 21:23 PDT
Thanks Archit for your comments.
I have addressed all of them in V3 and added Theirry Reading and Rob
Herring for reviews as well.
Abhinav
On 2018-04-19 10:44, Archit Taneja wrote:
Hi,
On Saturday 14 April 2018 12:55 PM, Abhinav Kumar wrote:
From: Archit Taneja
Hi, Stu:
On Wed, 2018-05-23 at 17:28 +0800, Stu Hsieh wrote:
> On Wed, 2018-05-23 at 13:23 +0800, CK Hu wrote:
> > Hi, Stu:
> >
> > I've some inline comment.
> >
> > On Wed, 2018-05-23 at 10:25 +0800, Stu Hsieh wrote:
> > > This patch add support for the Mediatek MT2712 DISP subsystem.
> > >
On Thu, May 24, 2018 at 4:31 AM, Daniel Vetter wrote:
> On Wed, May 23, 2018 at 2:59 PM, Qiang Yu wrote:
>> On Wed, May 23, 2018 at 5:04 PM, Daniel Vetter wrote:
>>> On Tue, May 22, 2018 at 09:04:17AM +0800, Qiang Yu wrote:
On Tue, May
Fixed image broken issue while video play back with 854x480.
GScaler device of Exynos5433 has IN_ID_MAX field in GSC_IN_CON
register, which determines how much GScaler DMA has to drain
data from system memory at once.
Therefore, image size should be fixed up before IPP driver verifies
whether
On Thu, May 24, 2018 at 1:24 AM, Rob Herring wrote:
> On Fri, May 18, 2018 at 05:27:58PM +0800, Qiang Yu wrote:
>> From: Lima Project Developers
>>
>> Signed-off-by: Qiang Yu
>> Signed-off-by: Heiko Stuebner
Yeah, the list is coming longer and longer, maybe I should just use
ARM || ARM64 || COMPILE_TEST
Regards,
Qiang
On Thu, May 24, 2018 at 1:26 AM, Rob Herring wrote:
> On Wed, May 23, 2018 at 07:16:41PM +0200, Marek Vasut wrote:
>> On 05/18/2018 11:28 AM, Qiang Yu wrote:
>> >
On Thu, May 24, 2018 at 1:12 AM, Marek Vasut wrote:
> On 05/18/2018 11:28 AM, Qiang Yu wrote:
>> GP is a processor for OpenGL vertex shader
>> processing.
>>
>> Signed-off-by: Qiang Yu
>
> [...]
>
>> +int lima_gp_init(struct lima_ip *ip)
>> +{
>> + struct
On Thu, May 24, 2018 at 8:48 AM, Kees Cook wrote:
> On Thu, Apr 26, 2018 at 4:25 PM, Kees Cook wrote:
>> On Thu, Mar 15, 2018 at 7:05 PM, Ben Skeggs wrote:
>>> On 14 March 2018 at 21:08, Thierry Reding
On Wed, May 23, 2018 at 11:44 PM, Daniel Vetter wrote:
> On Wed, May 23, 2018 at 3:52 PM, Qiang Yu wrote:
>> On Wed, May 23, 2018 at 5:29 PM, Christian König
>> wrote:
>>> Am 18.05.2018 um 11:27 schrieb Qiang Yu:
https://bugs.freedesktop.org/show_bug.cgi?id=106597
taij...@posteo.de changed:
What|Removed |Added
Attachment #139692|0 |1
is obsolete|
Hi, Noralf.
A couple of issues below:
On 05/23/2018 04:34 PM, Noralf Trønnes wrote:
This the beginning of an API for in-kernel clients.
First out is a way to get a framebuffer backed by a dumb buffer.
Only GEM drivers are supported.
The original idea of using an exported dma-buf was dropped
On Wed, May 23, 2018 at 12:30:59PM -0700, Jeykumar Sankaran wrote:
> Replace custom plane zpos property with drm core zpos
> property. CRTC relies on the normalized zpos values
> to configure blend stages of each plane.
>
> Signed-off-by: Jeykumar Sankaran
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=106517
Dhinakaran Pandiyan changed:
What|Removed |Added
CC|
On Wed, May 23, 2018 at 2:59 PM, Qiang Yu wrote:
> On Wed, May 23, 2018 at 5:04 PM, Daniel Vetter wrote:
>> On Tue, May 22, 2018 at 09:04:17AM +0800, Qiang Yu wrote:
>>> On Tue, May 22, 2018 at 3:37 AM, Eric Anholt wrote:
>>> > Qiang Yu
The device node iterators perform an of_node_get on each iteration, so a
jump out of the loop requires an of_node_put.
The semantic patch that fixes this problem is as follows
(http://coccinelle.lip6.fr):
//
@@
expression root,e;
local idexpression child;
iterator name for_each_child_of_node;
The device node iterators perform an of_node_get on each iteration, so a
jump out of the loop requires an of_node_put.
---
drivers/gpu/drm/rockchip/rockchip_lvds.c |4 +++-
drivers/pci/hotplug/pnv_php.c |8 ++--
drivers/phy/hisilicon/phy-hisi-inno-usb2.c |9
Remove hand rolled msm property caching to handle DPU
custom properties. This change also cleans up all its
dependencies to cache and restore respective drm
states.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/Makefile | 1 -
Replace custom plane zpos property with drm core zpos
property. CRTC relies on the normalized zpos values
to configure blend stages of each plane.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 36 +--
Remove dpu crtc custom properties and its handlers.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/Makefile | 1 -
drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c | 28 -
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 856
remove unwanted dpu uapi headers exposing custom
payload layouts for custom properties
Signed-off-by: Jeykumar Sankaran
---
include/uapi/drm/dpu_drm.h| 220 ---
include/uapi/drm/msm_drm_pp.h | 345 --
2
Enable drm core zpos normalization for planes.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/msm_drv.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/msm/msm_drv.c b/drivers/gpu/drm/msm/msm_drv.c
index ebc40a9..549359e 100644
---
Submitting a series of patches to further clean up DPU driver by stripping
down a list of custom properties supporting proprietary features. It
removes the property installers/handlers and cleans up relevant files of
of some of the advanced features. This series is based on the patch[1]
Cleanup residual connector property enumerations.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/msm_drv.h | 27 ---
1 file changed, 27 deletions(-)
diff --git a/drivers/gpu/drm/msm/msm_drv.h b/drivers/gpu/drm/msm/msm_drv.h
index
On Wed, May 23, 2018 at 01:00:01PM +0200, Marek Szyprowski wrote:
> Add all '1x' clocks to decon and decontv devices. Enabling those clocks
> is needed to get proper display on hardware windows no 4 and 5.
>
> Signed-off-by: Marek Szyprowski
> ---
>
On Tue, May 22, 2018 at 02:23:14AM +0300, Vladimir Zapolskiy wrote:
> The change adds support for Sharp LQ035Q7DB03 3.5" QVGA panel.
>
> Note that this aged panel is already found in the kernel sources,
> for instance in board mach files mach-mx21ads.c, mach-mx27ads.c,
> mach-pcm043.c, lpd270.c
://github.com/0day-ci/linux/commits/Ramalingam-C/drm-i915-Implement-HDCP2-2/20180523-031938
base: git://anongit.freedesktop.org/drm-intel for-linux-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones
On Sat, May 19, 2018 at 08:31:17PM +0200, Jernej Skrabec wrote:
> As already described in DT binding, TCON TOP is responsible for
> configuring display pipeline. In this initial driver focus is on HDMI
> pipeline, so TVE and LCD configuration is not implemented.
>
> Implemented features:
> - HDMI
On Sat, May 19, 2018 at 08:31:15PM +0200, Jernej Skrabec wrote:
> Video PLLs need to be referenced in R40 DT as possible HDMI PHY parent.
>
> Export them.
>
> Signed-off-by: Jernej Skrabec
> ---
> drivers/clk/sunxi-ng/ccu-sun8i-r40.h | 8 ++--
>
https://bugzilla.kernel.org/show_bug.cgi?id=199425
--- Comment #4 from Johannes Hirte (johannes.hi...@datenkhaos.de) ---
Sadly I don't have a reproducer for this. I'm starting the system, and after
some time I get the kasan-warning. Sometimes it happened really fast after
boot, sometimes it took
On Wed, May 23, 2018 at 07:16:41PM +0200, Marek Vasut wrote:
> On 05/18/2018 11:28 AM, Qiang Yu wrote:
> > From: Lima Project Developers
> >
> > Signed-off-by: Qiang Yu
> > Signed-off-by: Neil Armstrong
> >
On Fri, May 18, 2018 at 05:27:58PM +0800, Qiang Yu wrote:
> From: Lima Project Developers
>
> Signed-off-by: Qiang Yu
> Signed-off-by: Heiko Stuebner
> ---
> drivers/gpu/drm/lima/lima_regs.h | 304
https://bugzilla.kernel.org/show_bug.cgi?id=199425
mikita.lip...@amd.com (mikita.lip...@amd.com) changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=106499
Gregor Münch changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment
On Fri, May 18, 2018 at 05:27:52PM +0800, Qiang Yu wrote:
> From: Simon Shields
>
> v2 (Qiang Yu):
> add vender string to exynos4 mali gpu
This also needs to be added to the binding doc.
>
> Based off a similar commit for the Samsung Mali driver by
> Tobias Jakobi
On Fri, May 18, 2018 at 05:27:53PM +0800, Qiang Yu wrote:
> Signed-off-by: Qiang Yu
> ---
> Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt
>
https://bugs.freedesktop.org/show_bug.cgi?id=106631
Jan Vesely changed:
What|Removed |Added
Blocks||99553
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||106631
Referenced
https://bugs.freedesktop.org/show_bug.cgi?id=106634
--- Comment #7 from Michel Dänzer ---
Actually, it seems clear that this happens because 1 GB of VRAM and 3 GB of GTT
are full with buffer objects. Unless this keeps happening even immediately
after closing applications /
https://bugs.freedesktop.org/show_bug.cgi?id=106634
--- Comment #6 from udo ---
Created attachment 139719
--> https://bugs.freedesktop.org/attachment.cgi?id=139719=edit
journal
--
You are receiving this mail because:
You are the assignee for the
On Wed, May 23, 2018 at 06:07:49PM +0300, Laurent Pinchart wrote:
> Hi Lucas,
>
> (CC'ing Greg)
>
> On Wednesday, 23 May 2018 18:02:23 EEST Lucas Stach wrote:
> > Am Dienstag, den 22.05.2018, 13:37 +0300 schrieb Laurent Pinchart:
> > > On Tuesday, 22 May 2018 12:29:21 EEST Lucas Stach wrote:
> >
On Wed, May 23, 2018 at 11:25:04AM +0200, Marco Felsch wrote:
> From: Philipp Zabel
>
> This patch adds support for DLC DLC0700YZG-1 1024x600 LVDS panels
> to the simple-panel driver.
>
> Signed-off-by: Philipp Zabel
> [m.fel...@pengutronix.de:
https://bugs.freedesktop.org/show_bug.cgi?id=106634
--- Comment #5 from udo ---
There is no dmesg from before the problem occurs.
I will try the patch!
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106634
--- Comment #4 from Michel Dänzer ---
Created attachment 139718
--> https://bugs.freedesktop.org/attachment.cgi?id=139718=edit
Print fpfn/lpfn values in ttm_bo_mem_space_debug
Can you rebuild the ttm.ko module with this
https://bugs.freedesktop.org/show_bug.cgi?id=106634
Michel Dänzer changed:
What|Removed |Added
Summary|flip queue failed in|Failed to find
https://bugs.freedesktop.org/show_bug.cgi?id=106634
--- Comment #2 from udo ---
Created attachment 139717
--> https://bugs.freedesktop.org/attachment.cgi?id=139717=edit
xorg log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106634
udo changed:
What|Removed |Added
Summary|flip queue failed: Cannot |flip queue failed in
https://bugs.freedesktop.org/show_bug.cgi?id=106634
udo changed:
What|Removed |Added
Summary|some memory issue |flip queue failed: Cannot
https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #8 from Tapani Pälli ---
What comes to conformance, you should refer to latest OpenGL spec (now being
4.6). In this case you want to render to RGB32F we should take a look at
section "9.2.5 Required Renderbuffer
https://bugs.freedesktop.org/show_bug.cgi?id=106634
--- Comment #1 from udo ---
Created attachment 139716
--> https://bugs.freedesktop.org/attachment.cgi?id=139716=edit
messages
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106634
Bug ID: 106634
Summary: some memory issue
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
https://bugs.freedesktop.org/show_bug.cgi?id=106561
--- Comment #2 from Tomasz Paweł Gajc ---
Yes, previous libdrm versions were building without any issues on OpenMandriva
Lx.
I've already commited changes to spec file to use meson.
--
You are receiving this mail because:
On Wed, May 23, 2018 at 3:52 PM, Qiang Yu wrote:
> On Wed, May 23, 2018 at 5:29 PM, Christian König
> wrote:
>> Am 18.05.2018 um 11:27 schrieb Qiang Yu:
>>>
>>> Kernel DRM driver for ARM Mali 400/450 GPUs.
>>>
>>> This implementation mainly
Hi Lucas,
(CC'ing Greg)
On Wednesday, 23 May 2018 18:02:23 EEST Lucas Stach wrote:
> Am Dienstag, den 22.05.2018, 13:37 +0300 schrieb Laurent Pinchart:
> > On Tuesday, 22 May 2018 12:29:21 EEST Lucas Stach wrote:
> >> Am Sonntag, den 20.05.2018, 14:05 -0300 schrieb Fabio Estevam:
> From:
Hi Laurent,
Am Dienstag, den 22.05.2018, 13:37 +0300 schrieb Laurent Pinchart:
> Hi Lucas,
>
> On Tuesday, 22 May 2018 12:29:21 EEST Lucas Stach wrote:
> > Am Sonntag, den 20.05.2018, 14:05 -0300 schrieb Fabio Estevam:
> > > > From: Fabio Estevam
> > >
> > > Adopt the
We have had problems displaying fbdev after a resume and as a
workaround we have had to call vmw_fb_refresh(). This has had
a number of unwanted side-effects. The root of the problem was,
however that the coalesced fbdev dirty region was not empty on
the first dirty_mark() after a resume, so a
The error paths were leaking opened channels.
Fix by using dedicated error paths.
Cc:
Signed-off-by: Thomas Hellstrom
Reviewed-by: Brian Paul
Reviewed-by: Sinclair Yeh
---
drivers/gpu/drm/vmwgfx/vmwgfx_msg.c |
Depending on whether the kernel is compiled with frame-pointer or not,
the temporary memory location used for the bp parameter in these macros
is referenced relative to the stack pointer or the frame pointer.
Hence we can never reference that parameter when we've modified either
the stack pointer
https://bugs.freedesktop.org/show_bug.cgi?id=106625
Luke McKee changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #8
This switches the CMA helper drivers that use its fbdev emulation over
to the generic fbdev emulation. It's the first phase of using generic
fbdev. A later phase will use DRM client callbacks for the
lastclose/hotplug/remove callbacks.
There are currently 2 fbdev init/fini functions:
-
This is the first step in getting generic fbdev emulation.
A drm_fb_helper_funcs.fb_probe function is added which uses the
DRM client API to get a framebuffer backed by a dumb buffer.
A transitional hack for tinydrm is needed in order to switch over all
CMA helper drivers in a later patch. This
Add client callbacks and hook them up.
Add a list of clients per drm_device.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c| 246 +++-
drivers/gpu/drm/drm_debugfs.c | 7 +
drivers/gpu/drm/drm_drv.c |
This adds a drm_fbdev_generic_setup() function that sets up generic
fbdev emulation with client callbacks for lastclose, hotplug and
remove/unregister.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 123
It only makes sense for userspace clients.
Signed-off-by: Noralf Trønnes
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_file.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/drm_file.c
These are needed for pl111 to use the generic fbdev emulation.
Cc: Eric Anholt
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/pl111/pl111_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/pl111/pl111_drv.c
This the beginning of an API for in-kernel clients.
First out is a way to get a framebuffer backed by a dumb buffer.
Only GEM drivers are supported.
The original idea of using an exported dma-buf was dropped because it
also creates an anonomous file descriptor which doesn't work when the
buffer
Make ioctl wrappers for functions that will be used by the in-kernel API.
The following functions are touched:
- drm_mode_create_dumb_ioctl()
- drm_mode_destroy_dumb_ioctl()
- drm_mode_addfb()
- drm_mode_rmfb()
Signed-off-by: Noralf Trønnes
---
This patchset adds generic fbdev emulation for drivers that supports GEM
based dumb buffers which support .gem_prime_vmap and gem_prime_mmap. An
API is begun to support in-kernel clients in general.
The CMA helper drivers is moved as a whole over to this generic fbdev
emulation. I've added
From: David Herrmann
Rather than doing drm_file allocation/destruction right in the fops, lets
provide separate helpers. This decouples drm_file management from the
still-mandatory drm-fops. It prepares for use of drm_file without the
fops, both by possible separate fops
On Wed, May 23, 2018 at 10:19 PM, Christian König
wrote:
> Am 23.05.2018 um 16:13 schrieb Qiang Yu:
>>
>> On Wed, May 23, 2018 at 9:59 PM, Christian König
>> wrote:
>>>
>>> Am 23.05.2018 um 15:52 schrieb Qiang Yu:
On Wed, May 23, 2018
Am 23.05.2018 um 16:13 schrieb Qiang Yu:
On Wed, May 23, 2018 at 9:59 PM, Christian König
wrote:
Am 23.05.2018 um 15:52 schrieb Qiang Yu:
On Wed, May 23, 2018 at 5:29 PM, Christian König
wrote:
Am 18.05.2018 um 11:27 schrieb Qiang
On Wed, May 23, 2018 at 9:59 PM, Christian König
wrote:
> Am 23.05.2018 um 15:52 schrieb Qiang Yu:
>>
>> On Wed, May 23, 2018 at 5:29 PM, Christian König
>> wrote:
>>>
>>> Am 18.05.2018 um 11:27 schrieb Qiang Yu:
Kernel DRM
https://bugs.freedesktop.org/show_bug.cgi?id=106625
Christian König changed:
What|Removed |Added
Resolution|---
Am 23.05.2018 um 15:52 schrieb Qiang Yu:
On Wed, May 23, 2018 at 5:29 PM, Christian König
wrote:
Am 18.05.2018 um 11:27 schrieb Qiang Yu:
Kernel DRM driver for ARM Mali 400/450 GPUs.
This implementation mainly take amdgpu DRM driver as reference.
- Mali 4xx
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #1 from Ricardo Ribalda ---
Created attachment 139710
--> https://bugs.freedesktop.org/attachment.cgi?id=139710=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #2 from Ricardo Ribalda ---
libclc version: a2118d58fca567694edfabea78293e0dc9255500 (current HEAD)
--
You are receiving this mail because:
You are the assignee for the
On Wed, May 23, 2018 at 5:29 PM, Christian König
wrote:
> Am 18.05.2018 um 11:27 schrieb Qiang Yu:
>>
>> Kernel DRM driver for ARM Mali 400/450 GPUs.
>>
>> This implementation mainly take amdgpu DRM driver as reference.
>>
>> - Mali 4xx GPUs have two kinds of
https://bugs.freedesktop.org/show_bug.cgi?id=106631
Bug ID: 106631
Summary: PALM: clpeak: Bus error (core dumped) & lots of GPU
lockup
Product: Mesa
Version: 18.0
Hardware: Other
OS: All
Status:
Am 23.05.2018 um 15:13 schrieb Qiang Yu:
On Wed, May 23, 2018 at 5:35 PM, Christian König
wrote:
Well NAK, that brings back a callback we worked quite hard on getting rid
of.
It looks like the problem isn't that you need the preclose callback, but you
rather
On Wed, May 23, 2018 at 5:02 PM, Daniel Vetter wrote:
> On Fri, May 18, 2018 at 05:27:51PM +0800, Qiang Yu wrote:
>> Kernel DRM driver for ARM Mali 400/450 GPUs.
>>
>> This implementation mainly take amdgpu DRM driver as reference.
>>
>> - Mali 4xx GPUs have two kinds of
On Wed, May 23, 2018 at 5:35 PM, Christian König
wrote:
> Well NAK, that brings back a callback we worked quite hard on getting rid
> of.
>
> It looks like the problem isn't that you need the preclose callback, but you
> rather seem to misunderstood how TTM
On Wed, 16 May 2018, Jani Nikula wrote:
> Until now, the drm-intel commit access have been handed out ad hoc,
> without transparency, consistency, or fairness. With pressure to add
> more committers, this is no longer tenable, if it ever was. Document the
> requirements and
On Wed, May 23, 2018 at 5:04 PM, Daniel Vetter wrote:
> On Tue, May 22, 2018 at 09:04:17AM +0800, Qiang Yu wrote:
>> On Tue, May 22, 2018 at 3:37 AM, Eric Anholt wrote:
>> > Qiang Yu writes:
>> >
>> >> This reverts commit
1 - 100 of 185 matches
Mail list logo