I spoke with Rob on IRC about the set and he preferred the private
object be isolated in mdp5. So here's the atomic helper set rebased on
Archit's series.
One notable difference is that I've dropped the first patch from that
series which added a new private_obj lock to the core. Instead, it's
loc
From: Archit Taneja
Global shared resources (hwpipes, hwmixers and SMP) for MDP5 are
implemented as a part of atomic state by subclassing drm_atomic_state.
The preferred approach is to use the drm_private_obj infrastructure
available in the atomic core.
mdp5_global_state is introduced as a drm
From: Archit Taneja
This replaces the usage of the subclassed atomic state (mdp5_state)
with a private_obj state embedded within drm_atomic_state. The latter
method is the preferred approach, since it's simpler to implement
and less prone to errors.
The new API replaces the older and equivalent
Don't leave the event != NULL once it's consumed, this is used a signal
to the atomic helpers that the event will be handled by the driver.
Changes in v2:
- None
Changes in v3:
- Rebased on Archit's private_obj set
Cc: Jeykumar Sankaran
Reviewed-by: Archit Taneja
Signed-off-by: Sean Paul
---
Ensure that any queued events are issued when disabling the crtc. This
avoids timeouts when we come back and wait for dependencies (like the
previous frame's flip_done).
Changes in v2:
- None
Changes in v3:
- Rebased on Archit's private_obj set
Reviewed-by: Archit Taneja
Signed-off-by: Sean Paul
From: Archit Taneja
With the addition of "private_objs" in drm_atomic_state, we no longer
need to subclass drm_atomic_state to store state of share resources
that don't perfectly fit within planes/crtc/connector state information.
We can now save this state within drm_atomic_state itself using
th
Factor out the commit_tail() portions of complete_commit() into a
separate function to facilitate moving to the atomic helpers in future
patches.
Changes in v2:
- None
Changes in v3:
- Rebased on Archit's private_obj set
Cc: Jeykumar Sankaran
Reviewed-by: Archit Taneja
Signed-off-by: Sean Paul
Now that all of the msm-specific goo is tucked safely away we can switch
over to using the atomic helper commit directly. \o/
Changes in v2:
- None
Changes in v3:
- Rebased on Archit's private_obj set
Cc: Abhinav Kumar
Signed-off-by: Sean Paul
---
drivers/gpu/drm/msm/msm_atomic.c | 139 +--
Moving further towards switching fully to the the atomic helpers, this
patch removes the hand-rolled worker nonblock commit code and uses the
atomic helpers commit_work model.
Changes in v2:
- Remove commit_destroy()
- Shuffle order of commit_tail calls to further serialize commits
- Use stall in
https://bugzilla.kernel.org/show_bug.cgi?id=103881
--- Comment #5 from Jeffery Miller (jeffe...@gmail.com) ---
I tested this on 4.14.31 and it is fixed. It is able to sleep and resume
properly.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=103881
Jeffery Miller (jeffe...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Re
On Fri, Mar 30, 2018 at 11:39:05AM -0700, Eric Anholt wrote:
> Boris Brezillon writes:
>
> > ->atomic_async_update() requires that drivers update the plane->state
> > object before returning. Make sure at least common properties have been
> > updated.
> >
> > Cc: Gustavo Padovan
> > Signed-off-b
https://bugzilla.kernel.org/show_bug.cgi?id=103881
--- Comment #7 from Jeffery Miller (jeffe...@gmail.com) ---
I was also able to reproduce this issue on 4.16.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-de
https://bugzilla.kernel.org/show_bug.cgi?id=103881
--- Comment #8 from Jeffery Miller (jeffe...@gmail.com) ---
Comment 7 is wrong. I was unable to reproduce this issue on 4.16. It is fixed
in 4.16 and working as expected.
--
You are receiving this mail because:
You are watching the assignee of t
On Wed, Mar 21, 2018 at 8:40 PM, Rob Clark wrote:
> To all X.Org Foundation Members:
>
> The X.Org Foundation's annual election is now open and will remain
> open until 23:59 UTC on 5 April 2018.
Reminder that the elections are open until midnight on Thurs, so if
you have not already voted, pleas
On Mon, Apr 02, 2018 at 11:02:10AM -0600, Logan Gunthorpe wrote:
>
>
> On 30/03/18 01:45 PM, Jerome Glisse wrote:
> > Looking at upstream code it seems that the x86 bits never made it upstream
> > and thus what is now upstream is only for ARM. See [1] for x86 code. Dunno
> > what happen, i was co
On Fri, Mar 30, 2018 at 4:45 PM, Takashi Iwai wrote:
> amdgpu driver checks vgacon_text_force() after some initializations
> but without cleaning up. This will result in leaks.
>
> Move the check of vgacon_text_force() to the beginning of
> amdgpu_init() for fixing it and also for optimization.
>
On Mon, Apr 2, 2018 at 9:47 AM, Harry Wentland wrote:
> On 2018-03-30 12:00 PM, Colin King wrote:
>> From: Colin Ian King
>>
>> Trivial fix to spelling mistake in DRM_ERROR error message text
>>
>> Signed-off-by: Colin Ian King
>
> Reviewed-by: Harry Wentland
Applied. Thanks!
>
> Harry
>
>>
Maarten, Daniel,
Do we have any ww-mutex performance tests somewhere that can be used to
test the impact of implementation details on various locking scenarios?
Thanks,
/Thomas
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lis
Thanks for catching that. I'd use -ENODEV to match what is done a few
lines below for peer_pdd. With that fixed, this patch is Reviewed-by:
Felix Kuehling
Regards,
Felix
On 2018-03-29 10:25 PM, Wei Yongjun wrote:
> Passing NULL pointer to PTR_ERR will result in return value of 0
> indicating
This patch is Reviewed-by: Felix Kuehling
On 2018-03-29 10:25 PM, Wei Yongjun wrote:
> Fixes the following sparse warning:
>
> drivers/gpu/drm/amd/amdkfd/kfd_chardev.c:1150:6: warning:
> symbol 'kfd_dev_is_large_bar' was not declared. Should it be static?
>
> Signed-off-by: Wei Yongjun
> ---
>
Christian König writes:
> Hi Eric,
>
> nice to see that the scheduler gets used more and more.
>
> The feature your need to solve both your binning/rendering as well as
> your MMU problem is dependency handling. See the "dependency" callback
> of the backend operations.
>
> With this callback t
GEM objects mmap offsets are created by calling
drm_gem_create_mmap_offset_size() that doesn't need struct_mutex
protection as it includes its own locking, based on a size that is
static across the object's life time. Remove the unneeded struct_mutex
locking.
Signed-off-by: Laurent Pinchart
---
Hello,
This patch series removes the usage of struct_mutex from the omapdrm driver in
order to switch to gem_free_object_unlocked(). The series is inspired by
Daniel Vetter's recent gem_free_object_unlocked() patches (starting with
"[PATCH 1/5] staging/vboxvideo: Use gem_free_object_unlocked") and
From: Daniel Vetter
The only thing that omap_gem_free_object does that might need the magic
protection of struct_mutex (of keeping all objects alive if that lock is
held, even if the last reference is gone) is the mm_list manipulation.
This is already protected by the separate omapdrm->list_lock,
The __omap_gem_get_pages() function is a wrapper around
omap_gem_attach_pages() that returns the omap_obj->pages pointer through
a function argument. Some callers don't need the pages pointer, and all
of them can access omap_obj->pages directly. To simplify the code merge
the __omap_gem_get_pages()
From: Daniel Vetter
- None of the list walkings where protected.
- Switch to a mutex since the list walking could potentially take a
very long time.
Only thing we need to be careful with here is that while we walk the
list we cant unreference any gem objects, since the final unref would
resul
The DRM device struct_mutex is used to protect against concurrent GEM
object operations that deal with memory allocation and pinning. All
those operations are local to a GEM object and don't need to be
serialized across different GEM objects. Replace the struct_mutex with
a local omap_obj.lock or d
get_pages() as a local function name is too generic and easily confused
for a generic MM kernel function. Rename it to __omap_gem_get_pages().
Rename the is_contiguous(), is_cache_coherent(), evict(), evict_entry(),
fault_1d() and fault_2d() functions for the same reason.
Signed-off-by: Laurent P
On Mon, Apr 02, 2018 at 11:37:07AM -0600, Logan Gunthorpe wrote:
>
>
> On 02/04/18 11:20 AM, Jerome Glisse wrote:
> > The point i have been trying to get accross is that you do have this
> > information with dma_map_resource() you know the device to which you
> > are trying to map (dev argument t
https://bugs.freedesktop.org/show_bug.cgi?id=99403
--- Comment #6 from ilia ---
Glitches disappeared for me after graphics card upgrade to radeon 560. It very
possible means that amdgpu driver is not affected by this problem.
http://storage6.static.itmages.com/i/18/0402/h_1522696416_2964411_ae68b
To all X.Org Foundation Members:
Due to some technical difficulties, the earlier election notification
messages to memb...@x.org list did not go through (but also did not
trigger bounce/moderator notification). We cross referenced the
members list to the subscriber lists for xorg-devel, xorg, mes
On Mon, Apr 02, 2018 at 01:32:37PM -0600, Logan Gunthorpe wrote:
>
>
> On 02/04/18 01:16 PM, Jerome Glisse wrote:
> > There isn't good API at the moment AFAIK, closest thing would either be
> > lookup_resource() or region_intersects(), but a more appropriate one can
> > easily be added, code to w
https://bugs.freedesktop.org/show_bug.cgi?id=104825
Harry Wentland changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
While enabling/disabling DPMS before link training with MST hubs is
perfectly valid; unfortunately disabling DPMS results in some devices
disabling their AUX CH block as well. For SST this isn't as much of a
problem, but for MST we need to be able to continue handling aux
transactions even when non
While enabling/disabling DPMS before link training with MST hubs is
perfectly valid; unfortunately disabling DPMS results in some devices
disabling their AUX CH block as well. For SST this isn't as much of a
problem, but for MST we need to be able to continue handling aux
transactions even when non
On Mon, 2018-04-02 at 17:21 -0400, Lyude Paul wrote:
> While enabling/disabling DPMS before link training with MST hubs is
> perfectly valid; unfortunately disabling DPMS results in some devices
> disabling their AUX CH block as well. For SST this isn't as much of a
> problem, but for MST we nee
Latest version of https://patchwork.freedesktop.org/series/39642/ ,
hopefully patchwork understands this and doesn't break anything!
Lots of changes.
Lyude Paul (10):
drm/atomic: Print debug message on atomic check failure
drm/i915: Move DP modeset retry work into intel_dp
drm/dp_mst: Fix n
There's no reason to track the atomic state three times. Unfortunately,
this is currently what we're doing, and even worse is that there is only
one actually correct state pointer: the one in mst_state->base.state.
mgr->state never seems to be used, along with the one in
mst_state->state.
This con
While having the modeset_retry_work in intel_connector makes sense with
SST, this paradigm doesn't make a whole ton of sense when it comes to
MST since we have to deal with multiple connectors. In most cases, it's
more useful to just use the intel_dp struct since it indicates whether
or not we're d
Does what it says on the label, it's a little confusing debugging atomic
check failures otherwise.
Cc: Manasi Navare
Cc: Ville Syrjälä
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/drm_atomic.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_atomic.c
When a DP MST link needs retraining, sometimes the hub will detect that
the current link bw config is impossible and will update it's RX caps in
the DPCD to reflect the new maximum link rate. Currently, we make the
assumption that the RX caps in the dpcd will never change like this.
This means if t
The current way of handling changing VCPI allocations doesn't make a
whole ton of sense. Since drm_atomic_helper_check_modeset() can be
called multiple times which means that intel_dp_mst_atomic_check() can
also be called multiple times. However, since we make the silly mistake
of trying to free VC
Since these functions are dealing with an atomic state that needs to be
modified during atomic check and commit, change the naming on this
function to drm_atomic_dp_mst_get_topology_state() since we're the only
one using the function, and it's more consistent with the naming
scheme used in drm_atom
This gives drivers subclassing drm_dp_mst_topology_state the ability to
prepare their topology states for a new hub to be connected whenever
it's detected that the currently connected topology has been
disconnected from the system. We'll need this in order to correctly
track RX capabilities in i915
This is useful for drivers (which will probably be all of them soon)
which need to track state that is exclusive to the topology, and not a
specific connector on said topology. This includes things such as the
link rate and lane count that are shared by all of the connectors on the
topology.
Signe
For a while we actually haven't had any way of retraining MST links with
fallback link parameters like we do with SST. While uncommon, certain
setups such as my Caldigit TS3 + EVGA MST hub require this since
otherwise, they end up getting stuck in an infinite MST retraining loop.
MST retraining is
Unlike SST, MST can have far more then a single display hooked up on a
single port. What this also means however, is that if the DisplayPort
link to the top-level MST branch device becomes unstable then every
single branch device also has an unstable link. Additionally, MST has a
few more steps tha
On Mon, 2018-04-02 at 18:47 -0400, Lyude Paul wrote:
> There's no reason to track the atomic state three times. Unfortunately,
> this is currently what we're doing, and even worse is that there is only
> one actually correct state pointer: the one in mst_state->base.state.
> mgr->state never seems
https://bugs.freedesktop.org/show_bug.cgi?id=105317
--- Comment #6 from Timothy Arceri ---
Piglit test:
https://patchwork.freedesktop.org/patch/214341/
Mesa fix:
https://patchwork.freedesktop.org/patch/214346/
Note the WebGL test still froze in my testing but I think Firefox was
continuing to
On 04/02/2018 02:26 PM, Lyude Paul wrote:
While enabling/disabling DPMS before link training with MST hubs is
perfectly valid; unfortunately disabling DPMS results in some devices
disabling their AUX CH block as well. For SST this isn't as much of a
problem, but for MST we need to be able to cont
2018-03-28 23:22 GMT+08:00 Rob Herring :
> On Wed, Mar 28, 2018 at 10:19 AM, Rob Herring wrote:
>> On Sat, Mar 17, 2018 at 2:33 PM, Stefan Schake wrote:
>>> Hey John,
>>>
>>> On Fri, Mar 16, 2018 at 10:48 PM, John Stultz
>>> wrote:
In trying to integrate the new gralloc_handle.h with the
>
https://bugs.freedesktop.org/show_bug.cgi?id=90284
Timothy Arceri changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=90217
--- Comment #8 from Timothy Arceri ---
Hi guys,
There have been many improvements since this was reported, and I don't see any
other reports like this. Is this still happening or can we close this bug?
--
You are receiving this mail because:
Y
In trying to integrate the new gralloc_handle.h with the
drm_hwcomposer, I started seeing the following compilation
errors:
In file included from external/drm_hwcomposer/platformdrmgeneric.cpp:28:
external/libdrm/android/gralloc_handle.h:108:9: error: cannot initialize return
object of type 'nati
https://bugs.freedesktop.org/show_bug.cgi?id=89685
Timothy Arceri changed:
What|Removed |Added
CC||jarkko_ko...@hotmail.com
--- Comment #2
https://bugs.freedesktop.org/show_bug.cgi?id=89059
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=89685
Timothy Arceri changed:
What|Removed |Added
CC||kont...@ib-guder.de
--- Comment #26 fro
https://bugs.freedesktop.org/show_bug.cgi?id=89659
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEEDINFO
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Bug 99553 depends on bug 84232, which changed state.
Bug 84232 Summary: PHINode containing itself causes segfault in LLVM when
compiling Blender OpenCL kernel with R600 backend
https://bugs.freedesktop.org/show_bug.cgi?id=84232
What
https://bugs.freedesktop.org/show_bug.cgi?id=84232
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Rework the platformdrmgeneric buffer importer to use the libdrm
generic gralloc handle definition.
This is just to get the drm_hwcomposer project building in AOSP
along with the libdrm freedesktop/master branch. Similar changes
may also be needed to gbm_gralloc and other projects not used
in AOSP.
https://bugs.freedesktop.org/show_bug.cgi?id=94202
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=93649
--- Comment #79 from Timothy Arceri ---
*** Bug 95308 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing lis
https://bugs.freedesktop.org/show_bug.cgi?id=95308
Timothy Arceri changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=100393
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=101330
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=98351
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=99278
--- Comment #1 from Timothy Arceri ---
Are you still having this issue with recent Mesa / LLVM ?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
https://bugs.freedesktop.org/show_bug.cgi?id=100104
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=101746
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=91969
Timothy Arceri changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=105083
--- Comment #17 from Bogomil Vasilev ---
Experiencing this since 4.15 (not sure which minor release). Still happening on
4.16.0. With and without amdgpu=1, using RX480:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
E
https://bugs.freedesktop.org/show_bug.cgi?id=102342
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=89685
Timothy Arceri changed:
What|Removed |Added
CC||dogmad...@hotmail.com
--- Comment #27 f
https://bugs.freedesktop.org/show_bug.cgi?id=89954
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEEDINFO
https://bugs.freedesktop.org/show_bug.cgi?id=104696
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #1 from Timothy A
https://bugs.freedesktop.org/show_bug.cgi?id=99403
--- Comment #5 from Patrick Rudolph ---
Tested on llvmpipe and nvc0 (card NVD9): The bug isn't visible.
Tested on radeonsi (card AMD TAHITI): The bug is visible.
csmt_force makes no difference.
Mark as AMD bug.
Tested with mesa 17.3.0.
--
Yo
On Thursday 29 March 2018 07:54 PM, Ville Syrjälä wrote:
On Thu, Mar 29, 2018 at 07:39:07PM +0530, Ramalingam C wrote:
HDCP1.4 key can be loaded, only when Power well #1 is enabled and cdclk
is enabled. Using the I915 power well infrastruture, above requirement
is verified.
This patch enables
On Thursday 29 March 2018 08:05 PM, Sean Paul wrote:
On Thu, Mar 29, 2018 at 07:39:05PM +0530, Ramalingam C wrote:
As per DP spec when R0 mismatch is detected, HDCP source supported
re-read the R0 atleast twice.
And For HDMI and DP minimum wait required for the R0 availability is
100mSec. So
On Thursday 29 March 2018 08:08 PM, Sean Paul wrote:
On Thu, Mar 29, 2018 at 07:39:06PM +0530, Ramalingam C wrote:
In case of V prime mismatch, DP HDCP spec mandates the re-read of
Vprime atleast twice.
This patch needed for DP HDCP1.4 CTS Test: 1B-05.
v2:
Moved the V' validation into a f
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #13 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #10)
> Created attachment 138438 [details]
> Screenshot of the Blender window glitching
>
> I should add another detail to the discussion. I know this may be a separ
As per DP spec when R0 mismatch is detected, HDCP source supported
re-read the R0 atleast twice.
And For HDMI and DP minimum wait required for the R0 availability is
100mSec. So this patch changes the wait time to 100mSec but retries
twice with the time interval of 100mSec for each attempt.
This
In both HDMI and DP, device count is represented by 6:0 bits of a
register(BInfo/Bstatus)
So macro for bitmasking the device_count is fixed(0x3F->0x7F).
v3:
Retained the Rb-ed
Signed-off-by: Ramalingam C
cc: Sean Paul
Reviewed-by: Sean Paul
---
include/drm/drm_hdcp.h | 2 +-
1 file changed
In case of V prime mismatch, DP HDCP spec mandates the re-read of
Vprime atleast twice.
This patch needed for DP HDCP1.4 CTS Test: 1B-05.
v2:
Moved the V' validation into a function for retry. [Sean Paul]
v3:
Removed Inline keyword and DRM_DEBUG_KMS are used [Sean Paul]
Signed-off-by: Ramali
First two patches needed for below DP HDCP compliance tests
1A-06 and 1B-05
Third patch fixes the HDCP1.4 Key loadability check. where as fourth
one fixes the downstream device count read.
Fix for HDMI HDCP1.4 CTS tests: 1A-04 and 1A-07a are functional.
But the change from v2, as thinking
HDCP1.4 key can be loaded, only when Power well #1 is enabled and cdclk
is enabled. Using the I915 power well infrastruture, above requirement
is verified.
This patch enables the hdcp initialization for HSW, BDW, and BXT.
v2:
Choose the PW# based on the platform.
v3:
No Changes.
Signed-off-b
https://bugs.freedesktop.org/show_bug.cgi?id=104683
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=105317
Timothy Arceri changed:
What|Removed |Added
CC||freedesk...@linux-geek.org
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=104190
Timothy Arceri changed:
What|Removed |Added
CC||network...@rkmail.ru
--- Comment #4 fr
https://bugs.freedesktop.org/show_bug.cgi?id=103056
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=103769
Timothy Arceri changed:
What|Removed |Added
CC||negry.mis...@yandex.ru
--- Comment #13
https://bugs.freedesktop.org/show_bug.cgi?id=100990
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=100239
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=79895
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEEDINFO
As per DP spec when R0 mismatch is detected, HDCP source supported
re-read the R0 atleast twice.
And For HDMI and DP minimum wait required for the R0 availability is
100mSec. So this patch changes the wait time to 100mSec but retries
twice with the time interval of 100mSec for each attempt.
This
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #14 from MirceaKitsune ---
(In reply to iive from comment #13)
Like I said, I don't currently believe this is a hardware defect: My video card
isn't even 3 years old. It's a card from Gigabyte which makes high quality
products. The
Hi Kieran,
On Thursday, 29 March 2018 14:49:12 EEST Kieran Bingham wrote:
> Hi Laurent,
>
> Thank you for another patch :D
You're welcome, there will be more ;-)
> On 26/02/18 21:45, Laurent Pinchart wrote:
> > In order to make the vsp1_du_setup_lif() easier to read, and for
> > symmetry with t
https://bugs.freedesktop.org/show_bug.cgi?id=104190
--- Comment #5 from Kristian Nyborg Dahl ---
(In reply to Kristian Nyborg Dahl from comment #1)
> This was kisak-valve's comment on their github:
>
> "Hello @Heis, on my AMD test box, mesa 17.2.6 built against llvm 5.0.0 is
> affected, while l
Hi Kieran,
On Thursday, 29 March 2018 14:37:07 EEST Kieran Bingham wrote:
> On 26/02/18 21:45, Laurent Pinchart wrote:
> > When disabling a DRM plane, the corresponding RPF is only marked as
> > removed from the pipeline in the atomic update handler, with the actual
> > removal happening when conf
1 - 100 of 106 matches
Mail list logo