On Sat, Jun 18, 2016 at 04:41:26PM +0100, Chris Wilson wrote:
> On Sat, Jun 18, 2016 at 04:25:46PM +0100, Emil Velikov wrote:
> > On 18 June 2016 at 14:46, Chris Wilson wrote:
> > > 0-day kbuilder found
> > >
> > > [1.360244] BUG: unable to handle kernel NULL pointer dereference at
> > > (n
On Sat, Jun 18, 2016 at 04:20:47PM +0100, Chris Wilson wrote:
> Rendering operations to the dma-buf are tracked implicitly via the
> reservation_object (dmabuf->resv). The dmabuf sync ioctl allows
> userspace to wait upon outstanding rendering and prepare the object for
> CPU access (provided by th
On 18 June 2016 at 07:59, Vinay Simha wrote:
> On Sat, Jun 18, 2016 at 5:58 AM, Emil Velikov
> wrote:
>> Hi Vinay,
>>
>> On 17 June 2016 at 19:23, Vinay Simha BN wrote:
>>
>>> v6:
>>> * emil review comments incorporated
>>>PANEL_NUM_REGULATORS dropped, return ret added at necessary
>>>
,
||regression
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/d381654e/attachment-0
re the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/c08a8fb2/attachment.html>
Enable the standard GEM dma-buf interface provided by the DRM core, but
only for exporting the VGEM object. This allows passing around the VGEM
objects created from the dumb interface and using them as sources
elsewhere. Creating a VGEM object for a foriegn handle is not supported.
Testcase: igt/v
Hi Dave,
Just regression fixups and cleanups.
Since HW trigger mode was suppoted we have faced with a issue
that Display panel didn't work correctly when trigger mode was changed
in booting time.
For this, we keep trigger mode with SW trigger mode in default mode
like we did bef
iving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/1192c9a5/attachment-0001.html>
Signed-off-by: Julia Lawall
---
drivers/gpu/drm/nouveau/nvkm/engine/gr/gk20a.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/gr/gk20a.c
b/drivers/gpu/drm/nouveau/nvkm/engine/gr/gk20a.c
index 4ca8ed1..de8b806 100644
--- a/drivers/gpu/drm/nouveau/nvkm/e
On Fri, Jun 17, 2016 at 08:57:03PM +0200, Mathias Krause wrote:
> The callback function dma_buf_describe() returns an int not void so the
> function pointer cast in dma_buf_show() is wrong. dma_buf_describe() can
> also fail when acquiring the mutex gets interrupted so always returning
> 0 in dma_b
https://bugzilla.kernel.org/show_bug.cgi?id=120591
--- Comment #3 from Dmitrii Tcvetkov ---
Created attachment 220611
--> https://bugzilla.kernel.org/attachment.cgi?id=220611&action=edit
fix
Suggested by Ilia Mirkin
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=120591
--- Comment #4 from Dmitrii Tcvetkov ---
Thanks, that change helped, nouveau loaded successfully, Xorg started normally.
--
You are receiving this mail because:
You are watching the assignee of the bug.
..
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/5efee250/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=120591
--- Comment #5 from Dmitrii Tcvetkov ---
Created attachment 220621
--> https://bugzilla.kernel.org/attachment.cgi?id=220621&action=edit
dmesg with patched kernel
--
You are receiving this mail because:
You are watching the assignee of the bug
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/3756abe3/attachment.html>
|--- |FIXED
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/c0dced61/attachment.html>
:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/56df04df/attachment.html>
l.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/e49b7ab4/attachment.html>
TML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/cbab276f/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=120591
Dmitrii Tcvetkov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=119861
Dmitrii Tcvetkov changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #6 from Dmitrii Tc
ssignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/d3075b4e/attachment-0001.html>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/bee582f3/attachment.html>
- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/e99385bd/attachment.html>
.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/eb36b098/attachment.sig>
Hi,
The documentation of drm_atomic_helper_check_modeset() says:
"Drivers which update ->mode_changed (e.g. in their ->atomic_check hooks
if a plane update can't be done without a full modeset) _must_ call this
function afterwards after that change. It is permitted to call this
function multiple t
- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/89e2326b/attachment.html>
ent was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160619/b3866c14/attachment.html>
On Sun, Jun 19, 2016 at 9:57 PM, Jyri Sarha wrote:
> Hi,
> The documentation of drm_atomic_helper_check_modeset() says:
>
> "Drivers which update ->mode_changed (e.g. in their ->atomic_check hooks
> if a plane update can't be done without a full modeset) _must_ call this
> function afterwards afte
On Fri, 2016-06-17 at 16:06 -0700, James Bottomley wrote:
> On Fri, 2016-06-17 at 16:34 +0300, Jani Nikula wrote:
> > On Fri, 17 Jun 2016, Daniel Vetter wrote:
> > > On Thu, Jun 16, 2016 at 03:42:12PM -0700, James Bottomley wrote:
> > > > On Thu, 2016-06-16 at 14:29 -0700, James Bottomley wrote:
>
There is only a single user of dma_buf_debugfs_create_file() and that
one got the function pointer cast wrong. With that one fixed, there is
no need to have a wrapper for debugfs_create_file(), just call it
directly.
With no users left, we can remove dma_buf_debugfs_create_file().
While at it, si
The callback function dma_buf_describe() returns an int not void so the
function pointer cast in dma_buf_show() is wrong. dma_buf_describe() can
also fail when acquiring the mutex gets interrupted so always returning
0 in dma_buf_show() is wrong, too.
Fix both issues by avoiding the indirection vi
Change the error handling in dma_buf_init_debugfs() to remove the
"dma_buf" directory if creating the "bufinfo" file fails. No need to
have an empty debugfs directory around.
Signed-off-by: Mathias Krause
Cc: Sumit Semwal
Cc: Daniel Vetter
---
drivers/dma-buf/dma-buf.c |5 -
1 file cha
On 19 June 2016 at 10:45, Daniel Vetter wrote:
> On Fri, Jun 17, 2016 at 08:57:03PM +0200, Mathias Krause wrote:
>> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
>> index 6355ab38d630..0f2a4592fdd2 100644
>> --- a/drivers/dma-buf/dma-buf.c
>> +++ b/drivers/dma-buf/dma-buf.c
>>
This small series is the v2 of the patch posted initially here:
http://www.spinics.net/lists/linux-media/msg101347.html
It not only fixes the type mix-up and addresses Daniel's remark (patch 1),
it also smoothes out the error handling in dma_buf_init_debugfs() (patch 2)
and removes the then unn
35 matches
Mail list logo
