The reset value of the register is 0, the soft reset does not reset this
register and if other kernel changed this the audio is going to be
distorted.
It was observed when - accidentally - booted the kernel from eMMC on BBB
which is 3.8.13-bone79 and it sets this register to 0x0a. After reboot
From: Oleksandr Andrushchenko
Even if xen-front allocates its buffers from contiguous memory
those are still not contiguous in PA space, e.g. the buffer is only
contiguous in IPA space.
The only use-case for this mode was if xen-front is used to allocate
dumb
On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
> Yeah, I definitely agree on the idea of expanding the use case to the
> general domain where dmabuf sharing is used. However, what you are
> targetting with proposed changes is identical to the core design of
> hyper_dmabuf.
>
> On
https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #5 from taij...@posteo.de ---
Assuming that you mean amdgpu.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #4 from taij...@posteo.de ---
It is build as a module and then embedded in the initramfs.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
On Mon, Apr 16, 2018 at 06:10:07PM +0200, Noralf Trønnes wrote:
>
> Den 16.04.2018 10.46, skrev Daniel Vetter:
> > On Sat, Apr 14, 2018 at 01:53:14PM +0200, Noralf Trønnes wrote:
> > > These helpers keep track of fbdev users and drm_driver.last_close will
> > > only restore fbdev when actually in
Hi Sean,
Thank you for comments!
Could you please clarify a bit more here, as I've just
started recently working on drm side, so I took an
aspect ratio property as an example.
> @@ -491,6 +491,8 @@ static void intel_hdmi_set_avi_infoframe(struct
> drm_encoder *encoder,
>
https://bugs.freedesktop.org/show_bug.cgi?id=102638
--- Comment #5 from mj.wilson...@gmail.com ---
Please consider this resolved. At some point as mesa packages were upgraded,
this issue went away. I'm now on 17.3.6, and cannot reproduce the issue.
Thanks.
--
You are receiving this mail
On Tue, Apr 17, 2018 at 10:40:12AM +0300, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Even if xen-front allocates its buffers from contiguous memory
> those are still not contiguous in PA space, e.g. the buffer is only
> contiguous in IPA
Use new return type vm_fault_t for fault handler
in vm_operations_struct.
Signed-off-by: Souptick Joarder
---
drivers/gpu/drm/tegra/gem.c | 18 ++
1 file changed, 2 insertions(+), 16 deletions(-)
diff --git a/drivers/gpu/drm/tegra/gem.c
On Mon, Apr 16, 2018 at 09:19:21AM +0200, Andrzej Hajda wrote:
>
> +CC: linux-input list and maintainer
>
>
> On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
> > From: "Kristian H. Kristensen"
> >
> > To improve PSR exit latency, we speculatively start exiting when we
Colorkey'ing allows to draw on top of overlapping planes, like for example
on top of a video plane. Older Tegra's have a limited colorkey'ing
capability such that blending features are reduced when colorkey'ing is
enabled. In particular dependent weighting isn't possible, meaning that
cursors
On Mon 16 Apr 15:45 PDT 2018, abhin...@codeaurora.org wrote:
> Hi Bjorn
>
> Thanks for the review.
>
> Reply inline.
>
> On 2018-04-16 09:41, Bjorn Andersson wrote:
> > On Sat 14 Apr 00:25 PDT 2018, Abhinav Kumar wrote:
> >
> > > Register truly panel as a backlight led device and
> > >
On Sat 14 Apr 00:25 PDT 2018, Abhinav Kumar wrote:
> Register truly panel as a backlight led device and
> provide methods to control its backlight operation.
>
> Changes in v2:
> - Removed redundant NULL checks
> - Arranged headers alphabetically
> - Formatting fixes
The change log goes below
This new property allows userspace to apply custom color conversion
coefficients per plane, making possible to utilize display controller
for color adjustments of a video overlay.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/dc.c| 86
Older Tegra's do not support planes z position handling in hardware,
but HW provides knobs for zPos implementation in software.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/dc.c| 134 ---
drivers/gpu/drm/tegra/plane.c | 193
>>> drivers/gpu/drm/gma500/framebuffer.c:136:9: error: implicit declaration of
>>> function 'vmf_insert_mixed'; did you mean 'vm_insert_mixed'?
>>> [-Werror=implicit-function-declaration]
> ret = vmf_insert_mixed(vma, address,
> ^~~~
>cc1: some warnings being
On Mon, Apr 16, 2018 at 08:49:23PM +0200, Noralf Trønnes wrote:
>
> Den 16.04.2018 10.21, skrev Daniel Vetter:
> > On Sat, Apr 14, 2018 at 01:52:53PM +0200, Noralf Trønnes wrote:
> > > This patchset explores the possibility of having generic fbdev emulation
> > > in DRM for drivers that supports
On 04/17/2018 12:04 PM, Daniel Vetter wrote:
On Tue, Apr 17, 2018 at 10:40:12AM +0300, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Even if xen-front allocates its buffers from contiguous memory
those are still not contiguous in PA space, e.g.
:
https://github.com/0day-ci/linux/commits/Kristian-H-Kristensen/CHROMIUM-drm-rockchip-Disable-blending-for-win0/20180417-095916
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp
https://bugzilla.kernel.org/show_bug.cgi?id=199425
Bug ID: 199425
Summary: BUG: KASAN: use-after-free in
drm_atomic_helper_wait_for_flip_done+0x247/0x260
Product: Drivers
Version: 2.5
Kernel Version: 4.17-rc1
Hardware:
On Mon, Apr 16, 2018 at 03:16:28PM +0300, Dmitry Osipenko wrote:
> This new property allows userspace to apply custom color conversion
> coefficients per plane, making possible to utilize display controller
> for color adjustments of a video overlay.
>
> Signed-off-by: Dmitry Osipenko
On Mon, Apr 16, 2018 at 10:52:59AM -0700, Eric Anholt wrote:
> Chris Wilson writes:
>
> > Quoting Jordan Crouse (2018-04-05 23:06:53)
> >> On Thu, Apr 05, 2018 at 04:00:47PM -0600, Jordan Crouse wrote:
> >> > The i915 DRM driver very cleverly used ascii85 encoding for
On 04/17/2018 10:59 AM, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
Yeah, I definitely agree on the idea of expanding the use case to the
general domain where dmabuf sharing is used. However, what you are
targetting with proposed changes is identical to the
On Mon, Apr 16, 2018 at 03:16:27PM +0300, Dmitry Osipenko wrote:
> Colorkey'ing allows to draw on top of overlapping planes, like for example
> on top of a video plane. Older Tegra's have a limited colorkey'ing
> capability such that blending features are reduced when colorkey'ing is
> enabled. In
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #10 from Mathias Tillman (master.ho...@gmail.com) ---
Since that commit was pushed to v4.16, shouldn't it also be reverted on
linux-stable to make it to a future 4.16.y release?
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=105684
--- Comment #16 from jian-h...@endlessm.com ---
Created attachment 138874
--> https://bugs.freedesktop.org/attachment.cgi?id=138874=edit
dmesg of loading amdgpu module - tested in 4.17-rc1
I have tried Linux kernel 4.17-rc1 and load amdgpu
https://bugzilla.kernel.org/show_bug.cgi?id=199047
Johannes Hirte (johannes.hi...@datenkhaos.de) changed:
What|Removed |Added
Status|NEW |RESOLVED
On Mon, Apr 16, 2018 at 05:58:23PM +0200, Noralf Trønnes wrote:
>
> Den 16.04.2018 10.27, skrev Daniel Vetter:
> > On Sat, Apr 14, 2018 at 01:53:12PM +0200, Noralf Trønnes wrote:
> > > The modesetting code is already present, this adds the rest of the API.
> > Mentioning the TODO in the commit
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #31 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #29)
> For the first time ever, I might finally have some very good news on this
> issue! It will take several more days to confirm, then possibly another
> month to
On Tue, Apr 17, 2018 at 10:45:07AM +0530, Nautiyal, Ankit K wrote:
>
> On 4/6/2018 11:14 PM, Ville Syrjälä wrote:
> > On Fri, Apr 06, 2018 at 10:55:14PM +0530, Nautiyal, Ankit K wrote:
> > > This patch is causing failure of IGT test kms_3d. The kms_3d test
> > > expects the no. of 3d modes to be
Use new return type vm_fault_t for fault handler
in struct vm_operations_struct. For now, this is
just documenting that the function returns a VM_
FAULT value rather than an errno. Once all inst
ances are converted, vm_fault_t will become a di
stinct type.
Signed-off-by: Souptick Joarder
This patchset adds new custom plane / CRTC properties that are very useful
for displaying video overlay, they will be used by Opentegra Xorg driver.
Also generic zPos property is implemented for older Tegra's.
Dmitry Osipenko (4):
drm/tegra: plane: Implement zPos plane property for older
On Thu, 2018-04-05 at 11:49 +0200, Enric Balletbo i Serra wrote:
> From: "Kristian H. Kristensen"
>
> To improve PSR exit latency, we speculatively start exiting when we
> receive input events. Occasionally, this may lead to false positives,
> but most of the time we get a
Older Tegra's support blending. Rename SoC info entry supports_blending
to legacy_blending to eliminate confusion.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/dc.c | 20 ++--
drivers/gpu/drm/tegra/dc.h | 2 +-
2 files changed, 11 insertions(+), 11
Use new return type vm_fault_t for fault handler.
Signed-off-by: Souptick Joarder
Reviewed-by: Matthew Wilcox
---
drivers/gpu/drm/vgem/vgem_drv.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
Hi Archit,
On Monday, April 09, 2018 03:08 PM, Archit Taneja wrote:
>>> You could comment out the pm_runtime_put_sync() calls in
>>> drivers/gpu/drm/msm/dsi/dsi_host.c, in case some registers got
>>> reset during put_sync and weren't restored correctly after get_sync().
>>
>> That was my first
https://bugs.freedesktop.org/show_bug.cgi?id=101928
--- Comment #2 from i...@yahoo.com ---
The Ixit Nine issue has been closed.
The issue seems to be caused by running out of memory, due to a memory leak in
wine builtin OpenAL wrapper.
This could be workarounded by using native OpenAL32.dll or
Add mode_valid() function to filter modes according to available
pll clock values and "preferred" modes. It is particularly
useful for hdmi modes that require precise pixel clocks.
Note that "preferred" modes are always accepted:
- this is important for panels because panel clock tolerances are
On Tue, Apr 10, 2018 at 11:57 AM, Liviu Dudau wrote:
> I need to do a bit of archeology to get my Versatile Express back
> to working order in order to test your patches, which might not
> happen this week or so, but I have some comments on your approach
> which I would like
On Mon, Apr 16, 2018 at 5:52 PM, Eric Anholt wrote:
> The GPU subsystem node was a workaround to have a central device to
> bind V3D and display to. Following the lead of 246774d17fc0
> ("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove
> the subsystem node
On Sat, Apr 14, 2018 at 01:53:16PM +0200, Noralf Trønnes wrote:
> Add a notifier that fires when a new DRM device is registered.
> This can be used by the bootsplash client to connect to all devices.
>
> Signed-off-by: Noralf Trønnes
So I freaked out temporarily about your
https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #6 from taij...@posteo.de ---
If I wanted to try to embed amdgpu in the kernel for testing, how would I even
go about doing that? Simply editing my config file from =m to =y does not seem
to do anything.
--
You are receiving this
When video width is bigger than 3840 the linebuffer mode
should be LB_YUV_3840X5.
Signed-off-by: Sandy Huang
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
Hi Sandy,
Am Dienstag, 17. April 2018, 12:15:07 CEST schrieb Sandy Huang:
> When video width is bigger than 3840 the linebuffer mode
> should be LB_YUV_3840X5.
Can you explain that a bit better?
I.e. when looking at the code, the very first check is width > 2560.
So it seems your change
On Sun, Apr 8, 2018 at 3:08 AM, Eric Anholt wrote:
>> if (of_property_read_u32(dev->of_node, "max-memory-bandwidth",
>>>memory_bw)) {
>> dev_info(dev, "no max memory bandwidth specified, assume
>> unlimited\n");
>> @@ -275,7
When a driver related to one of the endpoints is deferred
due to probe dependencies (i2c, spi...) but the other one
is ready, ltdc probe continues and the deferred driver
will never be probed again.
The fix consists in waiting for all deferred endpoints before
continuing the ltdc probe.
Hi guys,
CCing: dri-devel.
question to the usual suspects here: Does somebody of hand knows when
DRM_RDWR was added and how we can check reliable if it's available or not?
Using the version number of amdgpu for this sounds a bit questionable,
cause that reflects amdgpu functionality level
On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote:
>>-Original Message-
>>From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
>>Sent: Wednesday, April 11, 2018 5:27 AM
>>To: Ian W MORRISON
>>Cc: Vivi, Rodrigo ;
On 17/04/18 13:32, Linus Walleij wrote:
[...]
Unfortunately there is just one single vexpress core tile in the
upstream kernel that define a CLCD controller, the CA9 (4xA9)
that I am using. All the others just use the MB CLCD.
I am thinking there is some never finished DTS upstreaming
here that
Quoting Jani Nikula (2018-04-17 12:02:52)
> On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote:
> >>-Original Message-
> >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
> >>Sent: Wednesday, April 11, 2018 5:27 AM
> >>To: Ian W MORRISON
On Wed, Apr 11, 2018 at 04:22:16PM +0100, Alexandru Gheorghe wrote:
> Use the newly added ResourceManager for creating and detecting all the
> drm devices instead of assuming that there is only one device.
>
> Signed-off-by: Alexandru Gheorghe
> ---
> index
Hi Sean,
On Mon, Apr 16, 2018 at 03:25:42PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:13PM +0100, Alexandru Gheorghe wrote:
> > vsyncworker::Routine assumes that when -EINTR is returned by
> > WaitForSignalOrExitLocked the lock as been released, which is not
> > true, so it hangs if
Hi Sean,
On Mon, Apr 16, 2018 at 03:54:02PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:16PM +0100, Alexandru Gheorghe wrote:
> > Use the newly added ResourceManager for creating and detecting all the
> > drm devices instead of assuming that there is only one device.
> >
> >
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #11 from Alex Deucher (alexdeuc...@gmail.com) ---
Yes, the revert cc'ed stable so it will show up in 4.16 as well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Hi Sean,
On Mon, Apr 16, 2018 at 03:59:07PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:17PM +0100, Alexandru Gheorghe wrote:
> > Writeback connector is a special case of connector, which can be
> > linked to a CRTC in order to get the result of the composition back to
> > a memory
On Tue, Apr 17, 2018 at 02:43:17PM +0100, Alexandru-Cosmin Gheorghe wrote:
> Hi Sean,
>
> On Mon, Apr 16, 2018 at 03:54:02PM -0400, Sean Paul wrote:
> > On Wed, Apr 11, 2018 at 04:22:16PM +0100, Alexandru Gheorghe wrote:
> > > Use the newly added ResourceManager for creating and detecting all the
Hi Rob,
On 09/04/18 21:17, Rob Herring wrote:
>>> For HDMI, you can't know in advance what resolution will be. So I
>>> think you always need to reserve 2 planes. Now, if you want to reduce
>>
>> We can decide not to support 2k+ resolutions for HDMI, which, with this
>> series, happens by not
On Mon, Apr 16, 2018 at 10:52:59AM -0700, Eric Anholt wrote:
> Chris Wilson writes:
>
> > Quoting Jordan Crouse (2018-04-05 23:06:53)
> >> On Thu, Apr 05, 2018 at 04:00:47PM -0600, Jordan Crouse wrote:
> >> > The i915 DRM driver very cleverly used ascii85 encoding for
On Mon, Apr 16, 2018 at 03:22:15PM -0700, Kristian H. Kristensen wrote:
> Blending win0 with the background color doesn't seem to work
> correctly. We only get the background color, no matter the contents of
> the win0 framebuffer. However, blending pre-multiplied color with the
> default opaque
On Mon, Apr 16, 2018 at 01:18:53PM +0100, Alexandru-Cosmin Gheorghe wrote:
> On Mon, Apr 16, 2018 at 12:30:13PM +0200, Robert Foss wrote:
>
> Hi Rob,
>
> Thanks for the review.
>
> > Hey Alexandru,
> >
> > Feel free to add:
> > Signed-off-by: Robert Foss
> >
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #32 from MirceaKitsune ---
(In reply to iive from comment #31)
Sounds a lot more complicated, but I'm gladly willing to try it as long as
there's no risk of anything permanently breaking my
On Wed, Apr 11, 2018 at 04:22:15PM +0100, Alexandru Gheorghe wrote:
> Add a resource manager object that is responsible for detecting all
> kms devices and allocates unique display numbers for every detected
> display.
>
> This is controlled by the value of hwc.drm.device property, if it ends
>
On Wed, Apr 11, 2018 at 04:22:21PM +0100, Alexandru Gheorghe wrote:
> When doing flattening of a composition on a different CRTC we need to be
> able to clone a layer in order to import it and then pass it to another CRTC.
>
> Signed-off-by: Alexandru Gheorghe
https://bugs.freedesktop.org/show_bug.cgi?id=97025
--- Comment #26 from Michel Dänzer ---
Does
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=daf8809626c0ee7a152f9c34058fc3b43385dd51
help for this?
--
You are receiving this mail because:
You
On Wed, Apr 11, 2018 at 04:22:20PM +0100, Alexandru Gheorghe wrote:
> When writeback connectors are available assign them to displays, in
> order to be able to use them for flattening of the current displayed
> scene. The pipeline for each display will look like this:
>
> CRTC encoder
On Tue, Apr 17, 2018 at 5:29 PM, Jani Nikula
wrote:
> On Tue, 17 Apr 2018, Souptick Joarder wrote:
>> Use new return type vm_fault_t for fault handler. For
>> now, this is just documenting that the function returns
>> a VM_FAULT value rather
On Wed, Apr 11, 2018 at 04:22:22PM +0100, Alexandru Gheorghe wrote:
> Add utility functions to copy the DrmHwcLayer and DrmCompositionPlanes
> from another DrmDisplayComposition.
>
> Signed-off-by: Alexandru Gheorghe
> ---
> drmdisplaycomposition.cpp | 29
On Tue, 17 Apr 2018, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
For dma_map_sg(), DMA API implementations are free to merge consecutive
segments into a single DMA mapping if conditions are suitable, thus the
resulting DMA addresses which drm_prime_sg_to_page_addr_arrays()
iterates may be packed into fewer entries than ttm->sg->nents implies.
The current
The amdgpu driver doesn't appear to directly use the scatterlist mapped
by amdgpu_ttm_tt_pin_userptr(), it merely hands it off to
drm_prime_sg_to_page_addr_arrays() to generate the dma_address array
which it actually cares about. Now that the latter can cope with
dma_map_sg() coalescing
Much like amdgpu, the radeon driver doesn't appear to directly use the
scatterlist mapped by radeon_ttm_tt_pin_userptr(), it merely hands it
off to drm_prime_sg_to_page_addr_arrays() to generate the dma_address
array which it actually cares about. Now that the latter can cope with
dma_map_sg()
Hey,
On 04/17/2018 05:33 PM, Sean Paul wrote:
On Wed, Apr 11, 2018 at 04:22:15PM +0100, Alexandru Gheorghe wrote:
Add a resource manager object that is responsible for detecting all
kms devices and allocates unique display numbers for every detected
display.
This is controlled by the value of
Am 17.04.2018 um 17:58 schrieb Robin Murphy:
For dma_map_sg(), DMA API implementations are free to merge consecutive
segments into a single DMA mapping if conditions are suitable, thus the
resulting DMA addresses which drm_prime_sg_to_page_addr_arrays()
iterates may be packed into fewer entries
On Wed, Apr 11, 2018 at 04:22:24PM +0100, Alexandru Gheorghe wrote:
> Currently Prepareframebuffer uses the mode of the connected connector
> to decide how big the buffer should be, however when using the
> drmdisplaycompositor just for flattening, the mode had not been set
> yet, so we need a way
https://bugzilla.kernel.org/show_bug.cgi?id=176311
--- Comment #7 from Michel Dänzer (mic...@daenzer.net) ---
Does
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=daf8809626c0ee7a152f9c34058fc3b43385dd51
help for this, by any chance?
BTW, I made a mistake in comment
On Wed, Apr 11, 2018 at 04:22:23PM +0100, Alexandru Gheorghe wrote:
> There is a lot of boilerplate for creating an initialized
> drmdisplaycomposition. This patch gathers that in a separate method.
>
> Signed-off-by: Alexandru Gheorghe
> ---
>
On Tue, 17 Apr 2018, Souptick Joarder wrote:
> On 17-Apr-2018 9:45 PM, "Matthew Wilcox" wrote:
>>
>> On Tue, Apr 17, 2018 at 09:14:32PM +0530, Souptick Joarder wrote:
>> > Not exactly. The plan for these patches is to introduce new vm_fault_t
> type
>>
s/PAGE_SIZE/PAGE_MASK/
Luckily release_offset is never larger than PAGE_SIZE, so the bug has no
bad side effects and managed to stay unnoticed for years that way ...
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_ioctl.c | 4 ++--
Gerd Hoffmann (2):
qxl: fix qxl_release_{map,unmap}
qxl: keep separate release_bo pointer
drivers/gpu/drm/qxl/qxl_drv.h | 1 +
drivers/gpu/drm/qxl/qxl_cmd.c | 6 ++
drivers/gpu/drm/qxl/qxl_ioctl.c | 4 ++--
drivers/gpu/drm/qxl/qxl_release.c | 18 +-
4 files
qxl expects that list_first_entry(release->bos) returns the first
element qxl added to the list. ttm_eu_reserve_buffers() may reorder
the list though.
Add a release_bo field to struct qxl_release and use that instead.
Signed-off-by: Gerd Hoffmann
---
On Tue, Apr 17, 2018 at 09:37:44AM -0400, Sean Paul wrote:
> On Mon, Apr 16, 2018 at 03:22:15PM -0700, Kristian H. Kristensen wrote:
> > Blending win0 with the background color doesn't seem to work
> > correctly. We only get the background color, no matter the contents of
> > the win0 framebuffer.
Hi Sean,
On Mon, Apr 16, 2018 at 04:02:07PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:18PM +0100, Alexandru Gheorghe wrote:
> > In the current implementation TryEncoderForDisplay just looks
> > at the crtc linked to the display, if that's not assigned to
> > a display it means the
Hi Sean,
On Mon, Apr 16, 2018 at 04:19:14PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:19PM +0100, Alexandru Gheorghe wrote:
> > drmModeEncoder has a field called possible_clones. It's a bit mask
> > which tells if the encoder could be simultaneously connected, to the
> > same CRTC,
On Tue, Apr 17, 2018 at 09:45:06AM -0400, Sean Paul wrote:
> On Mon, Apr 16, 2018 at 01:18:53PM +0100, Alexandru-Cosmin Gheorghe wrote:
> > On Mon, Apr 16, 2018 at 12:30:13PM +0200, Robert Foss wrote:
> >
> > Hi Rob,
> >
> > Thanks for the review.
> >
> > > Hey Alexandru,
> > >
> > > Feel free
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #33 from i...@yahoo.com ---
This doesn't sound good.
The sshd dying indicates that the kernel or the CPU has hang. If there is GPU
shader hang this doesn't happen right away, it usually waits 10 seconds before
attempting to reset the
https://bugs.freedesktop.org/show_bug.cgi?id=106110
Christoph Haag changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #34 from MirceaKitsune ---
(In reply to iive from comment #33)
Ahhh... you've reminded me of a detail that I have in fact noticed but forgot
to mention: After the machine freezes and becomes
On Tue, Apr 17, 2018 at 3:12 PM, Robin Murphy wrote:
> On 17/04/18 13:32, Linus Walleij wrote:
> [...]
>>
>> Unfortunately there is just one single vexpress core tile in the
>> upstream kernel that define a CLCD controller, the CA9 (4xA9)
>> that I am using. All the others
On Mon, Apr 16, 2018 at 06:56:45PM -0700, Abhinav Kumar wrote:
> Make sure the video mode engine is on before waiting
> for the video done interrupt.
>
> Changes in v2:
> - Replace pr_err with dev_err
> - Changed error message
>
> Changes in v3:
> - Move the return value check to another
>
https://bugzilla.kernel.org/show_bug.cgi?id=199319
--- Comment #16 from Harry Wentland (harry.wentl...@amd.com) ---
A fix should be in drm-next-4.17 of Alex's git repo at
https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.17 and should make it
into Linus's tree from there.
That fix should
Linus Walleij writes:
> On Sun, Apr 8, 2018 at 3:08 AM, Eric Anholt wrote:
>
>>> if (of_property_read_u32(dev->of_node, "max-memory-bandwidth",
>>>>memory_bw)) {
>>> dev_info(dev, "no max memory
On Tue, Apr 17, 2018 at 10:45:07AM +0530, Nautiyal, Ankit K wrote:
>
> On 4/6/2018 11:14 PM, Ville Syrjälä wrote:
> > On Fri, Apr 06, 2018 at 10:55:14PM +0530, Nautiyal, Ankit K wrote:
> >> This patch is causing failure of IGT test kms_3d. The kms_3d test
> >> expects the no. of 3d modes to be
On Mon, Apr 16, 2018 at 06:53:09PM +0300, Imre Deak wrote:
> LSPCON adapters in low-power state may ignore the first I2C write during
> TMDS output buffer enabling, resulting in a blank screen even with an
> otherwise enabled pipe. Fix this by reading back and validating the
> written value a few
https://bugs.freedesktop.org/show_bug.cgi?id=105083
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi Bjorn
Thanks for the comments.
Reply inline.
On 2018-04-16 23:13, Bjorn Andersson wrote:
On Mon 16 Apr 15:45 PDT 2018, abhin...@codeaurora.org wrote:
Hi Bjorn
Thanks for the review.
Reply inline.
On 2018-04-16 09:41, Bjorn Andersson wrote:
> On Sat 14 Apr 00:25 PDT 2018, Abhinav Kumar
On Wed, Apr 11, 2018 at 04:22:28PM +0100, Alexandru Gheorghe wrote:
> Flatten scene on the same CRTC as the one driving the display.
> The active composition is played back to the display with a buffer
> attached to the writeback connector.
> Then we build a composition that has only one plane
On Wed, Apr 11, 2018 at 04:22:26PM +0100, Alexandru Gheorghe wrote:
> Add a vsync worker that calls back into the DrmDisplayCompositor,
> for now at every 60 vsyncs if the scene does not change we trigger
> the flattening of the scene using the writeback connector.
> Other, more complex and proper
On Wed, Apr 11, 2018 at 04:22:25PM +0100, Alexandru Gheorghe wrote:
> ApplyFrame holds the lock just when it swaps the value of
> active_composition_, in a multithread context we could end up in a
> situation where something is shown on the screen, but something else
> is set in
On Wed, Apr 11, 2018 at 04:22:27PM +0100, Alexandru Gheorghe wrote:
> Add logic for finding a suitable writeback connector, there are two
> possibilities for finding an usable writeback connector:
>
> 1) Attached to the same CRTC as the display and can function
>concurrently with the display
1 - 100 of 141 matches
Mail list logo