tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 607b18ba116eb1642b01fb9d38a164cc492e9044 [2158/2647] drm/amdkcl: Test
whether vm_fault->{address/vma} is available
config: x86_64-randconfig-g002-201943 (attached
https://bugs.freedesktop.org/show_bug.cgi?id=111482
--- Comment #30 from Andrew Sheldon ---
(In reply to Shmerl from comment #29)
> Which one exactly did you set it at?
>
> I have 2560x1440 / 144 Hz monitor (LG 27GL850) and Sapphire Pulse RX 5700 XT
> (hardware switch set to higher performance
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: f2d51786363ee2a72c55570835e4c79066af2782 [2129/2647] drm/amdkcl: Test
whether kmap_atomic() wants one argument
config: x86_64-randconfig-g002-201943 (attached as
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: a54762aadc4f9bc23849aa01cac1ed8ad158ca3a [2121/2647] drm/amdkcl:
refactor drm_fb_helper_remove_conflicting_pci_framebuffers() check
config:
On Fri, Nov 01, 2019 at 04:06:40PM -0400, Lyude Paul wrote:
> Hi! Recently I've been working with the rest of the X.Org board to try to get
> X.org access to VESA memberships so that contributors that don't have an
> employer who is able/willing to join VESA can potentially get access to the
>
Hi, Sean:
On Fri, 2019-11-01 at 09:26 -0400, Sean Paul wrote:
> From: Sean Paul
>
> Expose the rotation property and handle REFLECT_Y rotations.
>
> Cc: Fritz Koenig
> Cc: Daniele Castagna
> Cc: Miguel Casas
> Cc: Mark Yacoub
> Signed-off-by: Sean Paul
> ---
>
> The hardware also
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 57d7e98d0257bd9795dd3f438d19aa5476554685 [2114/2647] drm/amdkcl: Test
whether drm_{mm_print/debug_printer} is available
config: x86_64-randconfig-g002-201943
Tested it on my end and confirmed that it works as intended.
On Fri, Nov 1, 2019 at 9:26 AM Sean Paul wrote:
>
> From: Sean Paul
>
> Expose the rotation property and handle REFLECT_Y rotations.
>
> Cc: Fritz Koenig
> Cc: Daniele Castagna
> Cc: Miguel Casas
> Cc: Mark Yacoub
> Signed-off-by:
According to VESA ENHANCED EXTENDED DISPLAY IDENTIFICATION DATA STANDARD
(Defines EDID Structure Version 1, Revision 4) page: 39
How to determine whether the monitor support RB timing or not?
EDID 1.4
First: read detailed timing descriptor and make sure byte0 = 0,
byte1 = 0, byte2 = 0 and
On Fri, Nov 1, 2019 at 11:33 AM Maarten Lankhorst
wrote:
>
> Op 01-11-2019 om 19:07 schreef Rob Clark:
> > From: Rob Clark
> >
> > The new state should not be accessed after this point. Clear the
> > pointers to make that explicit.
> >
> > This makes the error corrected in the previous patch
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c:339:22:
warning: variable srf set but not used [-Wunused-but-set-variable]
'srf' is never used, so can be removed.
Signed-off-by: YueHaibing
---
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 2 --
1 file changed, 2 deletions(-)
diff --git
On 2019/11/1 17:47, Thierry Reding wrote:
> On Thu, Oct 31, 2019 at 09:33:38PM +0800, Yuehaibing wrote:
>> On 2019/10/31 6:26, Dmitry Osipenko wrote:
>>> 30.10.2019 16:54, YueHaibing пишет:
If IOMMU_SUPPORT is not set, but IOMMU_IOVA is m and
COMPILE_TEST is y, building fails:
Hi Gabriela!
On 11/1/19 1:27 AM, Gabriela Bittencourt wrote:
> Add a description on VKMS module and the cases in which it should be used.
> There's a brief explanation on how to set it and use it in a VM, along with
> an example of running an igt-test.
>
> Signed-off-by: Gabriela Bittencourt
>
>
The function does not have a "dev" argument, so remove it from
the documentation. This fixes the following documentation
build warning:
./drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:335:
warning: Excess function parameter 'dev' description in
'amdgpu_gem_prime_export'
On Fri, Nov 1, 2019 at 12:25 PM Ville Syrjälä
wrote:
>
> On Fri, Nov 01, 2019 at 11:07:13AM -0700, Rob Clark wrote:
> > From: Rob Clark
> >
> > The new state should not be accessed after this point. Clear the
> > pointers to make that explicit.
> >
> > This makes the error corrected in the
The driver forgets to disable and unprepare clks when remove.
Add the calls to clk_disable_unprepare to fix the problem.
Signed-off-by: Chuhong Yuan
---
drivers/gpu/ipu-v3/ipu-prg.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/ipu-v3/ipu-prg.c b/drivers/gpu/ipu-v3/ipu-prg.c
On Fri, Nov 01, 2019 at 02:42:21PM -0300, Jason Gunthorpe wrote:
> On Fri, Nov 01, 2019 at 03:59:26PM +, Yang, Philip wrote:
> > > This test for range_blockable should be before mutex_lock, I can move
> > > it up
> > >
> > yes, thanks.
>
> Okay, I wrote it like this:
>
> if
On Mon, Oct 28, 2019 at 05:10:17PM -0300, Jason Gunthorpe wrote:
> From: Jason Gunthorpe
>
> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
> scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
> they only use invalidate_range_start/end and
On Fri, Nov 01, 2019 at 02:44:51PM +, Yang, Philip wrote:
>
>
> On 2019-10-29 3:25 p.m., Jason Gunthorpe wrote:
> > On Tue, Oct 29, 2019 at 07:22:37PM +, Yang, Philip wrote:
> >> Hi Jason,
> >>
> >> I did quick test after merging amd-staging-drm-next with the
> >> mmu_notifier branch,
Convert the collision-retry lock around hmm_range_fault to use the one now
provided by the mmu_range notifier.
Although this driver does not seem to use the collision retry lock that
hmm provides correctly, it can still be converted over to use the
mmu_range_notifier api instead of hmm_mirror
On Fri, Nov 01, 2019 at 03:59:26PM +, Yang, Philip wrote:
> > This test for range_blockable should be before mutex_lock, I can move
> > it up
> >
> yes, thanks.
Okay, I wrote it like this:
if (mmu_notifier_range_blockable(range))
mutex_lock(>notifier_lock);
On Fri, Nov 01, 2019 at 07:45:22PM +, Yang, Philip wrote:
> > This must be done inside the notifier_lock, after checking
> > mmu_range_read_retry(), all handling of the struct page must be
> > structured like that.
> >
> Below change will fix this, then driver will call mmu_range_read_retry
On Fri, Nov 01, 2019 at 02:44:51PM +, Yang, Philip wrote:
> @@ -854,12 +853,20 @@ int amdgpu_ttm_tt_get_user_pages(struct amdgpu_bo *bo,
> struct page **pages)
> r = -EPERM;
> goto out_unlock;
> }
> + up_read(>mmap_sem);
> + timeout = jiffies +
Small changes in the driver documentation, clarifing the description.
Signed-off-by: Gabriela Bittencourt
---
Tested using: make htmldocs
---
drivers/gpu/drm/vkms/vkms_drv.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/vkms/vkms_drv.c
On Fri, Nov 1, 2019 at 2:44 PM Ville Syrjälä
wrote:
>
> On Fri, Nov 01, 2019 at 12:49:02PM -0700, Rob Clark wrote:
> > On Fri, Nov 1, 2019 at 12:25 PM Ville Syrjälä
> > wrote:
> > >
> > > On Fri, Nov 01, 2019 at 11:07:13AM -0700, Rob Clark wrote:
> > > > From: Rob Clark
> > > >
> > > > The new
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 769e4dc19ad658720b779070764db2fc10a0bbac [2104/2647] drm/amdkcl: Test
whether drm_mm_insert_mode is available
config: x86_64-randconfig-g002-201943 (attached as
Changes in v2:
- Add fixing typo in word 'destination'
- Add change of the preposition
- In v1 the name of the function was wrong, fix it in this version
- Add the patch changing the word 'TODO'
I've tested the patches using kernel-doc
Gabriela Bittencourt (2):
drm/vkms: Fix typo and preposion
Changing the task introduction for the word 'TODO'. With the TODO word all
in uppercase, as is the standard, it's easier to find the tasks that have
to be done throughout the code.
Signed-off-by: Gabriela Bittencourt
---
drivers/gpu/drm/vkms/vkms_composer.c | 2 +-
1 file changed, 1
Fix typo in word 'blend' and in the word 'destination' and change
preposition 'at' to 'of' in function 'blend' documentation.
Signed-off-by: Gabriela Bittencourt
---
Changes in v2:
- Add fixing typo in word 'destination'
- Add change of the preposition
- In v1 the name of the function was
On Fri, Nov 01, 2019 at 12:49:02PM -0700, Rob Clark wrote:
> On Fri, Nov 1, 2019 at 12:25 PM Ville Syrjälä
> wrote:
> >
> > On Fri, Nov 01, 2019 at 11:07:13AM -0700, Rob Clark wrote:
> > > From: Rob Clark
> > >
> > > The new state should not be accessed after this point. Clear the
> > >
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 and maintainters:
Rebecca Schultz Zavin, Colin Cross, Laura Abbott, and others!
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 Android ION implementation, so
thanks to its original author and maintainters:
Benjamin Gaignard, Laura Abbott, and others!
NOTE: This patch only adds
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 to its original authors and maintainters:
Rebecca Schultz Zavin, Colin
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 device node, which a user can allocate
a dma-buf fd from using the DMA_HEAP_IOC_ALLOC.
Add very trivial allocation and import test for dma-heaps,
utilizing the vgem driver as a test importer.
A good chunk of this code taken from:
tools/testing/selftests/android/ion/ionmap_test.c
Originally by Laura Abbott
Cc: Benjamin Gaignard
Cc: Sumit Semwal
Cc: Liam Mark
Cc: Pratik
This again? I know!
Apologies to all who hoped I'd stop bothering them with this
patch set, but I ran afoul of the DRM tree rules by not
getting the userland patches properly reviewed prior to the
patches landing (I mistakenly was waiting for the patches to
land upstream before pushing the
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #11 from carben...@outlook.com ---
Seems to happen as well on 5.3.7 when waking two daisy-chained monitors from
sleep.
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Ellesmere [Radeon RX
On 2019-11-01 3:38 p.m., Jerry (Fangzhi) Zuo wrote:
> DP 1.4 edid corruption test requires source DUT to write calculated
> CRC, not the corrupted CRC from reference sink.
>
> Return the calculated CRC back, and initiate the required sequence.
>
> -v2: Have separate routine for returning real
On 10/28/19 1:10 PM, Jason Gunthorpe wrote:
From: Jason Gunthorpe
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating
On Mon, Oct 28, 2019 at 12:38:22PM +0200, Jani Nikula wrote:
> Add new struct drm_device based logging macros modeled after the core
> kernel device based logging macros. These would be preferred over the
> drm printk and struct device based macros in drm code, where possible.
>
> We have
On Mon, Oct 28, 2019 at 12:38:21PM +0200, Jani Nikula wrote:
> In preparation for adding struct drm_device based logging, group the
> existing functions by prink or struct device based logging. No
> functional changes.
>
> Signed-off-by: Jani Nikula
> ---
> include/drm/drm_print.h | 135
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #192 from Seba Pe ---
(In reply to L.S.S. from comment #188)
> Not sure where the problem might be.
>
> After installing 5.4-rc5, in addition to amdgpu-pro-libgl (and other
> amdgpu-pro related stuffs), I stopped encountering those
On Mon, Oct 28, 2019 at 12:38:19PM +0200, Jani Nikula wrote:
> We don't want people calling the functions directly. No functional
> changes.
>
> Signed-off-by: Jani Nikula
Reviewed-by: Rodrigo Vivi
> ---
> drivers/gpu/drm/drm_print.c | 8
> include/drm/drm_print.h | 22
Hi! Recently I've been working with the rest of the X.Org board to try to get
X.org access to VESA memberships so that contributors that don't have an
employer who is able/willing to join VESA can potentially get access to the
various benefits of a VESA membership, such as access to DisplayPort
On Fri, Nov 1, 2019 at 2:09 PM Rob Clark wrote:
>
> From: Rob Clark
>
> drm_self_refresh_helper_update_avg_times() was incorrectly accessing the
> new incoming state after drm_atomic_helper_commit_hw_done(). But this
> state might have already been superceeded by an !nonblock atomic update
>
Sorry, resend patch, the one in previous email missed couple of lines
duo to copy/paste.
On 2019-11-01 3:45 p.m., Yang, Philip wrote:
>
>
> On 2019-11-01 1:42 p.m., Jason Gunthorpe wrote:
>> On Fri, Nov 01, 2019 at 03:59:26PM +, Yang, Philip wrote:
This test for range_blockable should
On 2019-11-01 1:42 p.m., Jason Gunthorpe wrote:
> On Fri, Nov 01, 2019 at 03:59:26PM +, Yang, Philip wrote:
>>> This test for range_blockable should be before mutex_lock, I can move
>>> it up
>>>
>> yes, thanks.
>
> Okay, I wrote it like this:
>
> if
DP 1.4 edid corruption test requires source DUT to write calculated
CRC, not the corrupted CRC from reference sink.
Return the calculated CRC back, and initiate the required sequence.
-v2: Have separate routine for returning real CRC
Signed-off-by: Jerry (Fangzhi) Zuo
---
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 8aff76ca3bf3120204c9ec521ebe96a5133e92f3 [2094/2647] drm/amdkcl: Test
whether mmgrab is available
config: x86_64-randconfig-g002-201943 (attached as .config)
On Thu, Oct 31, 2019 at 4:07 AM Dan Carpenter wrote:
> The patch 7b87ea704fd9: "dma-buf: heaps: Add heap helpers" from Oct
> 21, 2019, leads to the following static checker warning:
>
> drivers/dma-buf/heaps/heap-helpers.c:165 dma_heap_vm_fault()
> warn: uncapped user index
On Fri, Nov 01, 2019 at 11:07:13AM -0700, Rob Clark wrote:
> From: Rob Clark
>
> The new state should not be accessed after this point. Clear the
> pointers to make that explicit.
>
> This makes the error corrected in the previous patch more obvious.
>
> Signed-off-by: Rob Clark
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #191 from wychuchol ---
Oh and music player kept working, played next track from playlist and I managed
to reset with REISUB.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #190 from wychuchol ---
Added AMD_DEBUG="nongg,nodma" to /etc/environment but it happened while opening
a webm file in a new tab in Palemoon.
Nov 1 20:10:30 pop-os kernel: [24044.197839]
[drm:amdgpu_dm_commit_planes.constprop.0
Hi Dave, Daniel,
More stuff for 5.5. Mostly bug fixes and cleanups at this point.
The following changes since commit 0e04ad7d1857670944786a8465930a049aaf995f:
drm/amdgpu/powerplay: use local renoir array sizes for clock fetching
(2019-10-25 16:48:14 -0400)
are available in the Git
Op 01-11-2019 om 19:07 schreef Rob Clark:
> From: Rob Clark
>
> The new state should not be accessed after this point. Clear the
> pointers to make that explicit.
>
> This makes the error corrected in the previous patch more obvious.
>
> Signed-off-by: Rob Clark
Would be nice if you could cc
On Fri, Nov 01, 2019 at 03:21:02PM -0300, Gabriela Bittencourt wrote:
> Fix typo in word 'blend' in function 'compute_crc' documentation.
>
> Signed-off-by: Gabriela Bittencourt
Reviewed-by: Manasi Navare
Manasi
> ---
> drivers/gpu/drm/vkms/vkms_composer.c | 2 +-
> 1 file changed, 1
Fix typo in word 'blend' in function 'compute_crc' documentation.
Signed-off-by: Gabriela Bittencourt
---
drivers/gpu/drm/vkms/vkms_composer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/vkms/vkms_composer.c
b/drivers/gpu/drm/vkms/vkms_composer.c
index
From: Rob Clark
The new state should not be accessed after this point. Clear the
pointers to make that explicit.
This makes the error corrected in the previous patch more obvious.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/drm_atomic_helper.c | 29 +
1 file
From: Rob Clark
drm_self_refresh_helper_update_avg_times() was incorrectly accessing the
new incoming state after drm_atomic_helper_commit_hw_done(). But this
state might have already been superceeded by an !nonblock atomic update
resulting in dereferencing an already free'd crtc_state.
Fixes:
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 3ba40228e28c15ca2dfec398cd7e5ebebdb5a9c2 [2082/2647] drm/amdkcl: Test
whether vmf_insert_*() functions are available
config: x86_64-randconfig-g002-201943 (attached
https://bugs.freedesktop.org/show_bug.cgi?id=112192
Alex Deucher changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
The pull request you sent on Fri, 1 Nov 2019 15:21:49 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-11-01
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/146162449186f95bf123f59fa57a2c28a8a075e5
Thank you!
--
Deet-doot-dot, I am a bot.
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: efcd1418868bc7be0eb22a57497ac20eeb831ff1 [2081/2647] drm/amdkcl: Test
whether memalloc_nofs_save() and memalloc_nofs_restore() functions are available
config:
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #189 from wychuchol ---
(In reply to Konstantin Pereiaslov from comment #187)
> As recommended here I added AMD_DEBUG="nongg,nodma" to /etc/environment and
> additionally added export AMD_DEBUG="nongg,nodma" to ~/.profile just to be
https://bugs.freedesktop.org/show_bug.cgi?id=111763
--- Comment #17 from wychuchol ---
(In reply to Andrew Sheldon from comment #16)
> (In reply to wychuchol from comment #14)
> > RX 5700 XT Pop OS 19.10 latest Oibaf mesa not sure what llvm
> > Anomaly 1.5.0 update 3 standalone 64 bit mod for
https://bugs.freedesktop.org/show_bug.cgi?id=107296
Janpieter Sollie changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
Op 01-11-2019 om 15:59 schreef Rob Clark:
> On Fri, Nov 1, 2019 at 7:47 AM Maarten Lankhorst
> wrote:
>> Op 31-10-2019 om 23:36 schreef Rob Clark:
>>> From: Rob Clark
>>>
>>> Stalling on cleanup_done ensures that any atomic state related to a
>>> nonblock commit no longer has dangling references
On 2019-11-01 11:12 a.m., Jason Gunthorpe wrote:
> On Fri, Nov 01, 2019 at 02:44:51PM +, Yang, Philip wrote:
>>
>>
>> On 2019-10-29 3:25 p.m., Jason Gunthorpe wrote:
>>> On Tue, Oct 29, 2019 at 07:22:37PM +, Yang, Philip wrote:
Hi Jason,
I did quick test after merging
Add a description on VKMS module and the cases in which it should be used.
There's a brief explanation on how to set it and use it in a VM, along with
an example of running an igt-test.
Signed-off-by: Gabriela Bittencourt
---
Changes in v2:
- Avoid repetition of words in the same sentence;
-
Hello,
as promised...
On Fri, Nov 01, 2019 at 08:58:03AM +, Lee Jones wrote:
> On Thu, 24 Oct 2019, Jacopo Mondi wrote:
>
> > Hello,
> >
> > On Thu, Oct 24, 2019 at 07:47:26AM +0100, Lee Jones wrote:
> > > On Wed, 23 Oct 2019, Daniel Thompson wrote:
> > >
> > > > On Tue, Oct 22, 2019 at
Add missing docbook comments to madvise fields in struct
drm_gem_shmem_object which fixes these warnings:
include/drm/drm_gem_shmem_helper.h:87: warning: Function parameter or member
'madv' not described in 'drm_gem_shmem_object'
include/drm/drm_gem_shmem_helper.h:87: warning: Function parameter
On Fri, Nov 1, 2019 at 7:47 AM Maarten Lankhorst
wrote:
>
> Op 31-10-2019 om 23:36 schreef Rob Clark:
> > From: Rob Clark
> >
> > Stalling on cleanup_done ensures that any atomic state related to a
> > nonblock commit no longer has dangling references to per-object state
> > that can be freed.
>
Op 31-10-2019 om 23:36 schreef Rob Clark:
> From: Rob Clark
>
> Stalling on cleanup_done ensures that any atomic state related to a
> nonblock commit no longer has dangling references to per-object state
> that can be freed.
>
> Otherwise, if a !nonblock commit completes after a nonblock commit
On Thu, Oct 31, 2019 at 07:03:59PM -0300, Fabio Estevam wrote:
> Hi Rob,
>
> On Tue, Oct 15, 2019 at 11:19 AM Jeffrey Hugo
> wrote:
> >
> > On Tue, Oct 15, 2019 at 7:40 AM Fabio Estevam wrote:
> > >
> > > Booting the adreno driver on a imx53 board leads to the following
> > > error message:
>
Op 31-10-2019 om 23:36 schreef Rob Clark:
> From: Rob Clark
>
> Stalling on cleanup_done ensures that any atomic state related to a
> nonblock commit no longer has dangling references to per-object state
> that can be freed.
>
> Otherwise, if a !nonblock commit completes after a nonblock commit
On 2019-10-29 3:25 p.m., Jason Gunthorpe wrote:
> On Tue, Oct 29, 2019 at 07:22:37PM +, Yang, Philip wrote:
>> Hi Jason,
>>
>> I did quick test after merging amd-staging-drm-next with the
>> mmu_notifier branch, which includes this set changes. The test result
>> has different failures, app
https://bugs.freedesktop.org/show_bug.cgi?id=112192
--- Comment #9 from Elmar Stellnberger ---
Ahh, I should have known. That is a detriment with the Debian live dvd.
Basically I could install the firmware with hindsight and then restart the
X-server.
There is another bug with the VESA
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #188 from L.S.S. ---
Not sure where the problem might be.
After installing 5.4-rc5, in addition to amdgpu-pro-libgl (and other amdgpu-pro
related stuffs), I stopped encountering those dreaded "ring sdma0 timeout"
freezes when using
https://bugs.freedesktop.org/show_bug.cgi?id=112192
--- Comment #8 from Alex Deucher ---
You need to install the firmware package:
[1.629363] [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel
modesetting for R600 or later requires firmware installed
--
You are receiving this mail
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: b35c23a557bb753b64082a4aa4057374bcbcca74 [2080/2647] drm/amdkcl: Test
whether kref_read() function is available
config: x86_64-randconfig-g002-201943 (attached as
Hi Maxime,
On Tue, Oct 29, 2019 at 2:24 PM Maxime Ripard wrote:
>
> On Tue, Oct 29, 2019 at 04:03:56AM +0530, Jagan Teki wrote:
> > > > explicit handling of common clock would require since the A64
> > > > doesn't need to mention the clock-names explicitly in dts since it
> > > > support only
On Wed, 30 Oct 2019, "Jerry (Fangzhi) Zuo" wrote:
> DP 1.4 edid corruption test requires source DUT to write calculated
> CRC, not the corrupted CRC from reference sink.
>
> Return the calculated CRC back, and initiate the required sequence.
>
> Signed-off-by: Jerry (Fangzhi) Zuo
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=112192
--- Comment #7 from Elmar Stellnberger ---
Created attachment 145869
--> https://bugs.freedesktop.org/attachment.cgi?id=145869=edit
dmesg from another boot with the same Debian Live CD
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=112192
Michel Dänzer changed:
What|Removed |Added
Product|xorg|DRI
Component|Driver/AMDgpu
On 01/11/2019 13:03, Emil Velikov wrote:
> From: Emil Velikov
>
> As of earlier commit we have address space separation. Yet we forgot to
> remove the respective comment and DRM_AUTH in the ioctl declaration.
>
> Cc: Tomeu Vizoso
> Cc: David Airlie
> Cc: Daniel Vetter
> Cc: Robin Murphy
>
From: Sean Paul
Expose the rotation property and handle REFLECT_Y rotations.
Cc: Fritz Koenig
Cc: Daniele Castagna
Cc: Miguel Casas
Cc: Mark Yacoub
Signed-off-by: Sean Paul
---
The hardware also supports REFLECT_X, but I just could not figure out
how to get it working. If someone is
From: Emil Velikov
Move the render_client hunk for require_exist alongside the rest.
Keeping all the reasons why an existing object is needed, in a single
place makes it easier to follow.
Cc: VMware Graphics
Cc: Thomas Hellstrom
Signed-off-by: Emil Velikov
---
From: Emil Velikov
As mentioned by Christian, for drivers which support only primary nodes
this changes the returned error from -EACCES into -EOPNOTSUPP/-ENOSYS.
For others, this check in particular will be a noop. So let's remove it
as suggested by Christian.
Cc: Alex Deucher
Cc:
From: Emil Velikov
With earlier commit 9c84aeba67cc ("drm/vmwgfx: Kill unneeded legacy
security features") we removed the no longer applicable validation, as
we now have isolation of primary clients from different master realms.
As of last commit, we're explicitly checking for authentication in
From: Emil Velikov
As of earlier commit we have address space separation. Yet we forgot to
remove the respective comment and DRM_AUTH in the ioctl declaration.
Cc: Tomeu Vizoso
Cc: David Airlie
Cc: Daniel Vetter
Cc: Robin Murphy
Cc: Steven Price
Fixes: 7282f7645d06 ("drm/panfrost:
From: Emil Velikov
With later commit we'll rework DRM authentication handling. Namely
DRM_AUTH will not be a requirement for DRM_RENDER_ALLOW ioctls.
Since vmwgfx does isolation for primary clients in different master
realms, the DRM_AUTH can be dropped.
The only place where authentication
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 034972ea50d821bd2596276c956b39f0ed9ca2dd [2071/2647] drm/amdkcl: Test
whether list_bulk_move_tail() is available
config: x86_64-randconfig-g002-201943 (attached as
tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
head: 00a7f0d7155c28ab18600bcf3f62d7cade2a870d
commit: 00a7f0d7155c28ab18600bcf3f62d7cade2a870d [2/2] drm/i915/tgl: Add perf
support on TGL
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-dirty
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 8d660d16d64cb75fab00f3e78409a93394cb7d29 [2055/2647] drm/amdkcl: Test
whether drm_dev_put is available
config: x86_64-randconfig-g002-201943 (attached as .config)
ATE to 20191021 (2019-10-21 12:56:07 +0300)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2019-11-01-1
for you to fetch changes up to 1883e2999f045e1fd6f76a7f30288a5312085289:
drm/i915: Update DRIVER_D
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: f12f9b802b6dd80fdee0b7c601b8b9d59a967556 [2031/2647] drm/amdkcl: Test
if linux/overflow.h and struct_size exists
config: x86_64-randconfig-g002-201943 (attached as
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: c53ae0e01db63d1b142681add947781668e3319c [2027/2647] drm/amdkcl: drop
kcl_dma_fence_set_error
config: x86_64-randconfig-g002-201943 (attached as .config)
compiler:
On Wed, Oct 30, 2019 at 06:05:48PM +0300, Dmitry Osipenko wrote:
> 28.10.2019 15:37, Thierry Reding пишет:
> > From: Thierry Reding
> >
> > All of the devices making up the Tegra DRM device want to share a single
> > IOMMU domain. Put them into a single group to allow them to do that.
> >
> >
On Thu, Oct 31, 2019 at 09:33:38PM +0800, Yuehaibing wrote:
> On 2019/10/31 6:26, Dmitry Osipenko wrote:
> > 30.10.2019 16:54, YueHaibing пишет:
> >> If IOMMU_SUPPORT is not set, but IOMMU_IOVA is m and
> >> COMPILE_TEST is y, building fails:
> >>
> >> drivers/gpu/host1x/dev.o: In function
etnaviv supports the following pipe types:
ETNA_PIPE_3D 0x00
ETNA_PIPE_2D 0x01
ETNA_PIPE_VG 0x02
The current used value of 4 for ETNA_MAX_PIPES is wrong and
caueses some troubles in the combination with perf counters.
Lets have a look at the function etnaviv_pm_query_dom(..):
If
1 - 100 of 148 matches
Mail list logo
