search for: fb_ids

drmmode_set_scanout_pixmap(pix) adds drmmod->fb_id through a call to drmmode_xf86crtc_resize(), but on a subsequent drmmode_set_scanout_pixmap(NULL) it would not remove the fb. This keeps the crtc marked as busy, which causes the dgpu to not being able to runtime suspend, after an output attached to the dgpu has been used once. Which causes burning through an additional 10W of power and the

Apparently it now wants a drawable. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- No idea about whether this is correct. Saw the new warnings though. src/drmmode_display.c | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 2480122..f677e24 100644 --- a/src/drmmode_display.c +++

Hi Ilia, Ben, et al. Can I please get a review of this patch, and assuming the review is favorable, can someone please push this ? Regards, Hans p.s. Is it ok if I request push rights to the nouveau repos / group at freedesktop.org ? On 03-06-16 14:46, Hans De Goede wrote: > drmmode_set_scanout_pixmap(pix) adds drmmod->fb_id through a call > to drmmode_xf86crtc_resize(), but on a

Hi all, I wanted to test requests from internal facebook apps, so I''ve been mimicking FBML requests from facebook in my tests using the following: def test_can_facebook_internal_app_login fb_login_as :facebooker num_of_members = Member.count facebook_request :get, :home assert_response :success assert_equal num_of_members, Member.count

Apologies for not chaning the subject line. :( Hi all, I wanted to test requests from internal facebook apps, so I''ve been mimicking FBML requests from facebook in my tests using the following: def test_can_facebook_internal_app_login fb_login_as :facebooker num_of_members = Member.count facebook_request :get, :home assert_response :success assert_equal

From: Lyude Paul <lyude at redhat.com> There's been a TODO sitting in the kms_plane test suite for a while now as a placeholder for actually generating a reference CRC for plane-position-hole tests. This means we have never actually been verifying whether or not partially covering our hole with a hardware plane works displays properly, and have just simply been checking that the frame

Hi My name is Rocky and I am trying to use the org.Dm.eg.db library. When I am using the org.Dm.egFLYBASE2EG[fb_ids] it is stopping at a point where it cannot find any value for a given ID such as the following: Error in .checkKeys(value, Rkeys(x), x@ifnotfound) : value for "FBgn0004461" not found Then the whole thing stops. I cannot retrieve any information on the values that has been found until th...

Hi all, First thing first: It works, I now no longer have a few dropped frames every 10s on my testbox here with the pageflip i-g-t tests. Random notes: - New design has per-crtc locks to protect the crtc input-side (pageflip, cursor) for r/w and the output state of the crtc (mode, dpms) as read-only. It also required completely revamped fb lifecycle management, those are now refcounted

From: Michel Dänzer <michel.daenzer at amd.com> This allows making the master screen's pixmap_dirty_list entries explicitly reflect that we're now tracking the root window instead of the screen pixmap, in order to allow Present page flipping on master outputs while there are active slave outputs. Define HAS_DIRTYTRACKING_DRAWABLE_SRC for drivers to check, but leave

https://bugs.freedesktop.org/show_bug.cgi?id=66255 Priority: medium Bug ID: 66255 Assignee: nouveau at lists.freedesktop.org Summary: Enabling Xinerama with nouveau driver causes Segmentation fault QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS: Linux (All)

Hi, here a set of patches against the nouveau-ddx. This is an extended and revised set, based on Francisco Jerez feedback from autumn last year. [1/9] Makes pageflipping work again on X-Server 1.12rc. It apparently stopped working somewhere around Xorg 1.11+. [2/9] Implements handling of pageflip completion events from the kernel. Francisco Jerez argument against including it was that the

From: Lyude Paul <lyude at redhat.com> We're finally getting CRC support in nouveau, so let's start testing this in igt as well! While the normal CRC capture tests are nice, there's a number of Nvidia-specific hardware characteristics that we need to test as well. The most important one is known as a "notifier context flip". Basically, Nvidia GPUs store generated CRCs

From: Lyude Paul <lyude at redhat.com> We're finally getting CRC support in nouveau, so let's start testing this in igt as well! While the normal CRC capture tests are nice, there's a number of Nvidia-specific hardware characteristics that we need to test as well. The most important one is known as a "notifier context flip". Basically, Nvidia GPUs store generated CRCs

From: Lyude Paul <lyude at redhat.com> We're finally getting CRC support in nouveau, so let's start testing this in igt as well! While the normal CRC capture tests are nice, there's a number of Nvidia-specific hardware characteristics that we need to test as well. The most important one is known as a "notifier context flip". Basically, Nvidia GPUs store generated CRCs

...an.new_worker( :worker => :update_facebook_account_info_worker, :job_key => @some.id, # Only run one worker per id :data => { :session_key => @session_key, :requesting_fb_id => @organizer.facebook_id, :facebook_ids => @fb_ids, :params => params } ) The output... create=>{:params=>REDACTED]} Some read error Some read error Some read error Thanks Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/background...

I'm pleased to announce the 7.9.0 release of xf86-video-ati, the Xorg driver for ATI/AMD Radeon GPUs supported by the radeon kernel driver. This release supports xserver versions 1.10-1.19. NOTE for packagers: Please ship the new 10-radeon.conf file in the same package as radeon_drv.so. Highlights: * Allow TearFree to be toggled at runtime via an RandR output property

I'm pleased to announce the 7.7.0 release of xf86-video-ati, the Xorg driver for ATI/AMD Radeon GPUs supported by the radeon kernel driver. This release supports xserver versions 1.9-1.18. Highlights: * Option "TearFree" can now prevent tearing with rotation/reflection as well (with Xorg >= 1.16). * RandR CRTC transforms now work correctly (but for now still exhibit tearing

Thanks for the quick review! On Tue, Aug 1, 2017 at 5:09 AM, Laurent Pinchart <laurent.pinchart@ ideasonboard.com> wrote: > Hi Joe, > > Thank you for the patch. > > On Monday 31 Jul 2017 11:29:13 Joe Kniss wrote: > > New getfb2 functionality uses drm_mode_fb_cmd2 struct to be symmetric > > with addfb2. > > What's the use case for this ? We haven't

New getfb2 functionality uses drm_mode_fb_cmd2 struct to be symmetric with addfb2. Also modifies *_fb_create_handle() calls to accept a format_plane_index so that handles for each plane can be generated. Previously, many *_fb_create_handle() calls simply defaulted to plane 0 only. Signed-off-by: Joe Kniss <djmk at google.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 5 +-

I'm pleased to announce the 1.1.0 release of xf86-video-amdgpu, the Xorg driver for AMD Radeon GPUs supported by the amdgpu kernel driver. This release supports xserver versions 1.9-1.18. Highlights: * Support for the upcoming Polaris family of GPUs. * Option "TearFree" can now prevent tearing with rotation/reflection as well (with Xorg >= 1.16). * RandR CRTC transforms now