On 19 March 2018 at 14:41, Eric Engestrom wrote:
> On Monday, 2018-03-19 06:47:32 -0700, John Stultz wrote:
>> Building libdrm under AOSP, we see the following build warning:
>> external/libdrm/xf86drm.c:2861:12: warning: 'readdir_r' is deprecated:
>> readdir_r is deprecated; use readdir instead
On Tuesday, 2018-03-20 17:48:23 +, Emil Velikov wrote:
> From: John Stultz
>
> Building libdrm under AOSP, we see the following build warning:
> external/libdrm/xf86drm.c:2861:12: warning: 'readdir_r' is deprecated:
> readdir_r is deprecated; use readdir instead [-Wdeprecated-declarations]
>
Replace drm_gem_object_reference/unreference function with *_get/put()
suffixes, because it is shorter and consistent with the kernel
kref_get/put() functions. The following Coccinelle script was used:
@@
expression e;
@@
(
-drm_gem_object_reference(e);
+drm_gem_object_get(e);
|
-drm_gem_object_u
On Tuesday, 2018-03-20 17:36:51 +, Emil Velikov wrote:
> From: Tomasz Figa
>
> This patch makes the code not rely anymore on libpciaccess when compiled
> for Android to eliminate ioperm() and iopl() syscalls required by that
> library. As a side effect, the mappable aperture size is hardcoded
On Tuesday, 2018-03-20 17:46:36 +, Eric Engestrom wrote:
> First 5 patches fix a bug where $driver=auto could end up being turned
> on even though a dependency (`with_atomic`) is missing.
>
> Next 4 are turning auto=false into auto=true, which I guess might not be
> what we want. I'm happy to
https://bugs.freedesktop.org/show_bug.cgi?id=100726
--- Comment #11 from hiwatari.se...@gmail.com ---
I can confirm this is still a problem (tested 4.15.10).
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
From: Ville Syrjälä
Currently we're leaking fbs on load detect on account of nothing setting
up plane->old_fb for the drm_atomic_clean_old_fb() call in
drm_atomic_helper_commit_duplicated_state(). Removing the
drm_atomic_clean_old_fb() call seems like the right call to me here.
This does mean we
From: Ville Syrjälä
Keep the primary->crtc in sync with the state->crtc (also with
primary->fb and state->fb) when disabling the crtc (and thus also
the primary) via setcrtc().
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/drm_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
From: Ville Syrjälä
drm_atomic_helper_commit_duplicated_state() should only be called
resume/reset/load_detect paths where plane->old_fb should always be
NULL and plane->fb should be equal to the new_plane_state->fb.
Assert that is indeed the case.
Cc: martin.pe...@free.fr
Cc: ch...@chris-wilson
From: Ville Syrjälä
When doing forced load detection testing we should totally ignore any
hotplug status for the connector. This is mostly relevant for machines
where we already ignore the hotplug status based on the DMI quirks. On
other machines we would currently skip the force load detection t
From: Ville Syrjälä
drm_atomic_helper_shutdown() needs to release the reference held by
plane->fb, so we want to use drm_atomic_clean_old_fb() in
drm_atomic_helper_disable_all(). However during suspend/resume, gpu
reset and load detection we should probably leave that stuff alone,
as otherwise we
From: Ville Syrjälä
Actually turn the planes back on after were done with
the load detection.
Fixes: 20bdc112bbe4 ("drm/i915: Disable all planes for load detection, v2.")
Cc: Maarten Lankhorst
Cc: Daniel Vetter
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_display.c | 2 ++
1 f
https://bugs.freedesktop.org/show_bug.cgi?id=105632
Bug ID: 105632
Summary: X won't start at "drm/amd/pp: Simplified the avfs btc
state on smu7"
Product: DRI
Version: DRI git
Hardware: Other
OS: All
On Tue, Mar 20, 2018 at 03:16:08PM +, Alexandru-Cosmin Gheorghe wrote:
> On Tue, Mar 20, 2018 at 10:00:17AM -0400, Sean Paul wrote:
> > On Tue, Mar 13, 2018 at 04:21:20PM +, Alexandru Gheorghe wrote:
> > > This patchset tries to add support for using writeback connector to
> > > flatten a s
From: Yinghai Lu
Add support for arbitrary bus address offset. Previously we ignored the
child (PCI) address in the "ranges" property and assumed it was always
zero. That means every host bridge window mapped to PCI bus address zero,
e.g.,
pci_bus :00: root bus resource [mem 0x20
From: Bjorn Helgaas
Previously, pci_register_legacy_regions() reserved PCI address space under
every PCI host bridge for the System ROM and the Video ROM, but these
regions are not part of PCI address space.
Previously, pci_register_legacy_regions() reserved the following areas of
PCI address sp
On Mon, Mar 19, 2018 at 07:33:41PM -0400, David Miller wrote:
> From: Bjorn Helgaas
> Date: Mon, 19 Mar 2018 14:38:54 -0500
>
> > I'd be happy to remove both. But I wonder how X init works on
> > sparc.
>
> It's been many years since I worked on this, but I think it
> mapped and used the PCI RO
These are from an old series from Yinghai [1] that fix some issues on
sparc64. The v1 posting is at [2].
[1] https://lkml.kernel.org/r/20170421050500.13957-1-ying...@kernel.org
[2]
https://lkml.kernel.org/r/20180215151118.196756.99622.st...@bhelgaas-glaptop.roam.corp.google.com
Changes from v1:
https://bugs.freedesktop.org/show_bug.cgi?id=105632
--- Comment #1 from Alex Deucher ---
Fixed with this patch:
https://patchwork.freedesktop.org/patch/211482/
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mail
https://bugs.freedesktop.org/show_bug.cgi?id=105633
Bug ID: 105633
Summary: [amdgpu][bisected] PRIME stuttering tearing
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
S
From: Bjorn Helgaas
Date: Tue, 20 Mar 2018 15:14:01 -0500
> These are from an old series from Yinghai [1] that fix some issues on
> sparc64. The v1 posting is at [2].
>
> [1] https://lkml.kernel.org/r/20170421050500.13957-1-ying...@kernel.org
> [2]
> https://lkml.kernel.org/r/20180215151118.19
https://bugs.freedesktop.org/show_bug.cgi?id=60879
--- Comment #173 from madmalkav ---
As it has failed to attract any developer attention in for two years, I have
cancelled the bountysource reward.
From: bugzilla-dae...@freedesktop.org
Sent: Saturday, November 4
https://bugs.freedesktop.org/show_bug.cgi?id=105632
charlie changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
getfb can only return a single plane, so reject attempts to use it with
multi-plane framebuffers.
Signed-off-by: Daniel Stone
Reported-by: Daniel van Vugt
Fixes: 308e5bcbdb10 ("drm: add an fb creation ioctl that takes a pixel format
v5")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=10
Hi Dave,
Updates for 4.17. Sorry, running a bit late on this, didn't have a
chance to send pull-req before heading to linaro. But it has all been
in linux-next for a while. Main updates:
+ DSI updates from 10nm / SDM845
+ fix for race condition with a3xx/a4xx fence completion irq
+ some ref
On Tue, Mar 20, 2018 at 6:58 PM, Daniel Stone wrote:
> getfb can only return a single plane, so reject attempts to use it with
> multi-plane framebuffers.
>
yeah, this seems like a pretty good idea,
Reviewed-by: Rob Clark
> Signed-off-by: Daniel Stone
> Reported-by: Daniel van Vugt
> Fixes:
On Tue, Mar 20, 2018 at 11:16 AM, Alexandru-Cosmin Gheorghe
wrote:
> On Tue, Mar 20, 2018 at 10:00:17AM -0400, Sean Paul wrote:
>> On Tue, Mar 13, 2018 at 04:21:20PM +, Alexandru Gheorghe wrote:
>> > This patchset tries to add support for using writeback connector to
>> > flatten a scene when
https://bugs.freedesktop.org/show_bug.cgi?id=105639
Bug ID: 105639
Summary: System hangs up when loading amdgpu module
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Sev
https://bugs.freedesktop.org/show_bug.cgi?id=105639
--- Comment #1 from Alex Deucher ---
You built the driver without display support. Please make sure your .config
has the following set:
CONFIG_DRM_AMD_DC=y
CONFIG_DRM_AMD_DC_DCN1_0=y
--
You are receiving this mail because:
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=105530
--- Comment #5 from txtsd ---
(In reply to Michel Dänzer from comment #4)
> (In reply to txtsd from comment #0)
> > The stuttering is caused by enabling TearFree via xrandr.
> > When on `auto`, there is no stuttering, but when enabled by setting
101 - 130 of 130 matches
Mail list logo
