On 17.02.2017 18:06, Ilia Mirkin wrote:
> On Fri, Feb 17, 2017 at 11:22 AM, João Paulo Rechi Vita
> wrote:
>> Hello Ilia,
>>
>> On 17 February 2017 at 11:14, Ilia Mirkin wrote:
>>> On Fri, Feb 17, 2017 at 10:54 AM, João Paulo Rechi Vita
>>>
On 08.11.2016 07:47, Dave Airlie wrote:
> From: Dave Airlie
>
> Thou shall not send control msg from the stack,
> does that mean I can send it from the RO memory area?
>
> and it looks like the answer is no, so here's
> v2 which kmemdups.
>
> Reported-by: poma
&
On 08.11.2016 07:39, Dave Airlie wrote:
> From: Dave Airlie
>
> Thou shall not send control msg from the stack,
> does that mean I can send it from the RO memory area?
>
> Reported-by: poma
> Signed-off-by: Dave Airlie
> ---
> drivers/gpu/drm/udl/udl_main.c | 8 ++
On 23.08.2016 07:57, Daniel Vetter wrote:
> On Mon, Aug 22, 2016 at 11:17:34PM +0100, Jamie Lentin wrote:
>> Lift configuration command from udlfb. This appears to be essential for
>> at least a Rextron VCUD-60, without which no URB communication occurs.
>>
>> Signed-off-by: Jamie Lentin
>> ---
On 19.09.2016 23:12, Daniel Vetter wrote:
> On Mon, Sep 19, 2016 at 8:27 PM, poma wrote:
>> @@ -122,14 +126,14 @@ int udl_handle_damage(struct udl_framebuffer *fb, int
>> x, int y,
>> return 0;
>> cmd = urb->transfer_buffer;
>>
&
On 21.09.2016 13:33, David Herrmann wrote:
> Hi
>
> On Wed, Sep 21, 2016 at 1:19 PM, poma wrote:
>> On 21.09.2016 09:34, David Herrmann wrote:
>>> Hi
>>>
>>> On Wed, Sep 21, 2016 at 6:47 AM, poma wrote:
>>>> Within X server, on top
On 21.09.2016 09:34, David Herrmann wrote:
> Hi
>
> On Wed, Sep 21, 2016 at 6:47 AM, poma wrote:
>> Within X server, on top of DisplayLink GPU USB2.0 device,
>> screen content is not refreshed i.e. updated.
>>
>> This fixes commit:
>>
>> - e37588240
Within X server, on top of DisplayLink GPU USB2.0 device,
screen content is not refreshed i.e. updated.
This fixes commit:
- e375882406d0cc24030746638592004755ed4ae0
"drm/udl: Use drm_fb_helper deferred_io support"
Thanks Noralf and Daniel for the comments.
Tested-by: poma
---
d
:
- e375882406d0cc24030746638592004755ed4ae0
"drm/udl: Use drm_fb_helper deferred_io support"
Thanks Noralf for the comments.
Reported and
Tested-by: poma
---
drivers/gpu/drm/udl/udl_fb.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/udl/udl_fb.c b/drivers/g
On 18.09.2016 19:42, Noralf Trønnes wrote:
>
> Den 18.09.2016 15:48, skrev poma:
>> Fix for DisplayLink GPU USB2.0 device X server screen update
>>
>> Within X server on top of DisplayLink GPU USB2.0 device,
>> screen content is not refreshed i.e. updat
42.158940] [drm] Initialized udl on minor 1
[ 42.159676] usbcore: registered new interface driver udl
$ grep udl /var/log/Xorg.0.log
[71.194] (**) | |-->Device "udl0"
Tested-by: poma
---
drivers/gpu/drm/udl/udl_drv.h | 2 ++
drivers/gpu
https://bugzilla.redhat.com/show_bug.cgi?id=1375566
Guys,
do you use such a device - DisplayLink GPU USB2.0 ?
>
> - drm_gem_object_unreference(>base);
> + drm_gem_object_unreference_unlocked(>base);
> *handle_p = handle;
> return 0;
> }
>
Reviewed-by: poma
First Kangaroo: What does a frog say when it washes car windows?
Second Kangaroo: Rub it, rub it, rub it.
https://lists.freedesktop.org/archives/dri-devel/2016-January/097945.html
https://patchwork.freedesktop.org/patch/65722
https://bugzilla.redhat.com/show_bug.cgi?id=1295646
It's been more
On 23.11.2015 10:33, Daniel Vetter wrote:
> vgem doesn't have a shrinker or anything like that and drops backing
> storage only at object_free time. There's no use in trying to be
> clever and allocating backing storage delayed, it only causes trouble
> by requiring locking.
>
> Instead grab
On 05.01.2016 09:49, Daniel Vetter wrote:
> On Tue, Jan 05, 2016 at 08:46:19AM +0100, poma wrote:
>>
>> Hi Fi
>>
>> Please take a loo kat
>> https://bugzilla.redhat.com/show_bug.cgi?id=1295646
>
> Patches to fix these have been hanging around on t
Hi Fi
Please take a loo kat
https://bugzilla.redhat.com/show_bug.cgi?id=1295646
On 12.11.2015 14:48, Thierry Reding wrote:
> On Wed, Nov 11, 2015 at 09:12:33PM +0100, poma wrote:
>> On 10.11.2015 17:25, Mario Kleiner wrote:
>>> On 11/10/2015 05:00 PM, Thierry Reding wrote:
>>>> On Tue, Nov 10, 2015 at 03:54:52PM +0100, Mario Kleiner wr
On 15.12.2015 12:21, Emil Velikov wrote:
> On 15 December 2015 at 11:11, poma wrote:
>
>>
>> Apparently not reached @stable (stable: 4.3.3 2015-12-15),
>> so here's one more time.
>>
> It has reached 4.4-rcX and will get picked by the stable maintainer
> (G
On 10.11.2015 17:41, Thierry Reding wrote:
> On Tue, Nov 10, 2015 at 05:37:31PM +0100, Thierry Reding wrote:
>> From: Daniel Vetter
>>
>> Apparently pre-nv50 pageflip events happen before the actual vblank
>> period. Therefore that functionality got semi-disabled in
>>
>> commit
On 02.12.2015 09:55, Daniel Vetter wrote:
> On Wed, Dec 02, 2015 at 06:40:32AM +0100, poma wrote:
>> On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner
>> wrote:
>>> When we are at it, the one with the title "[PATCH] drm/nouveau: Use
>>> drm_vblank_on/of
On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner
wrote:
> When we are at it, the one with the title "[PATCH] drm/nouveau: Use
> drm_vblank_on/off consistently" from Daniel, which has a reviewed and tested
> by me also never made it into nouveau.
>
> Maybe pick that up as well?
>
> -mario
>
If you
On Mon, Nov 16, 2015 at 4:11 PM, Daniel Vetter wrote:
> On Mon, Nov 02, 2015 at 04:45:00PM +0900, Michel Dänzer wrote:
>> On 31.10.2015 06:55, Daniel Vetter wrote:
>> > Apparently pre-nv50 pageflip events happen before the actual vblank
>> > period. Therefore that functionality got semi-disabled
On 12.11.2015 14:48, Thierry Reding wrote:
> On Wed, Nov 11, 2015 at 09:12:33PM +0100, poma wrote:
>> On 10.11.2015 17:25, Mario Kleiner wrote:
>>> On 11/10/2015 05:00 PM, Thierry Reding wrote:
>>>> On Tue, Nov 10, 2015 at 03:54:52PM +0100, Mario Kleiner wr
On 10.11.2015 17:25, Mario Kleiner wrote:
> On 11/10/2015 05:00 PM, Thierry Reding wrote:
>> On Tue, Nov 10, 2015 at 03:54:52PM +0100, Mario Kleiner wrote:
>>> From: Daniel Vetter
>>>
>>> Apparently pre-nv50 pageflip events happen before the actual vblank
>>> period. Therefore that functionality
ase_unmap(qdev, *release, info);
> -
> - qxl_bo_unref();
> return 0;
> }
>
>
Tested with:
- Rawhide-Xfce-Live-1001.iso
\ 4.3.0-0.rc3.git2.4.fc24.x86_64
+ v2-1-2-drm-qxl-avoid-buffer-reservation-in-qxl_crtc_page_flip.patch
+ v2-2-2-drm-qxl-avoid-dependency-lock.patch
Tested-by: poma
Does virtgpu provides the same or a similar mechanism as QXL virtual GPU does?
Dynamic guest resizing related.
Ref.
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/qxl/qxl_display.c?id=4695b03
[0.00] Linux version 3.18.0-0.rc0.git2.1.fc22.x86_64 (mockbuild at
bkernel01.phx2.fedoraproject.org) (gcc version 4.9.1 20140930 (Red Hat
4.9.1-11) (GCC) ) #1 SMP Thu Oct 9 13:57:38 UTC 2014
[0.00] Command line:
BOOT_IMAGE=/vmlinuz-3.18.0-0.rc0.git2.1.fc22.x86_64
h completion, so one doesn't pars it via e.g. dmesg -t |
grep -P '(?=.*devices)(?=.*USB)', grep -B1 sys /var/log/Xorg.0.log, tree
/sys/class/drm, etc.
Behind the wheel, dri/drm device 'sys' path doesn't show up in dmesg,
nor in Xorg.*.log. - cc'ing dri-devel.
Cheers,
poma
completion, so one doesn't pars it via e.g. dmesg -t |
grep -P '(?=.*devices)(?=.*USB)', grep -B1 sys /var/log/Xorg.0.log, tree
/sys/class/drm, etc.
Behind the wheel, dri/drm device 'sys' path doesn't show up in dmesg,
nor in Xorg.*.log. - cc'ing dri-devel.
Cheers,
poma
30 matches
Mail list logo