From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ilija Hadzic Subject: Re: [RFC v2] Revive the work on render-nodes branch Date: Thu, 12 Apr 2012 14:09:13 -0500 (CDT) Message-ID: References: <1334254784-3200-1-git-send-email-ihadzic@research.bell-labs.com> <20120412185526.GN4917@intel.com> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1817792895-1334257753=:18467" Return-path: Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by gabe.freedesktop.org (Postfix) with ESMTP id 739C39E7B0 for ; Thu, 12 Apr 2012 12:09:18 -0700 (PDT) In-Reply-To: <20120412185526.GN4917@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-1817792895-1334257753=:18467 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 12 Apr 2012, Ville [iso-8859-1] Syrj=E4l=E4 wrote: > Didn't have time for a detailed look yet, but at least one thing > missing from your patch set is handling of possible_crtcs and > possible_clones for getplane and getencoder ioctls. Yes I agree and I know. That is still work in progress. The ioctl for=20 constructing the node should do more checks not only for possible_crtcs=20 and possible_clones, but also whether a particular encoder can match the=20 connector and not allow creation of the node with incompatible resources.= =20 I have all that on the TODO list, but I wanted to get the patches out=20 early so that I can get some feedback (and hopefully motivate others to=20 contribute). There will definitely be v3 (and beyond) that will include stuff on my=20 TODO list along with any feedback that I receive. > Also the name "render node" is still very confusing. How about just > callling it a partition or something. Or maybe someone could suggest > a more self explanatory name for this stuff. > Dave has chosen the name two years ago when he did the initial demo work.= =20 I am just keeping this name for now (the advantage is that others know of= =20 this work by this name, so they know what it is about). However, if there= =20 is a concensus for a better name I'll be glad to adopt it. -- Ilija ---559023410-1817792895-1334257753=:18467 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ---559023410-1817792895-1334257753=:18467--