Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757333AbcJXLLK (ORCPT ); Mon, 24 Oct 2016 07:11:10 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34295 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753962AbcJXLLJ (ORCPT ); Mon, 24 Oct 2016 07:11:09 -0400 MIME-Version: 1.0 In-Reply-To: <20161021171240.6972-2-eric@anholt.net> References: <20161021171240.6972-1-eric@anholt.net> <20161021171240.6972-2-eric@anholt.net> From: Emil Velikov Date: Mon, 24 Oct 2016 12:11:07 +0100 Message-ID: Subject: Re: [PATCH libdrm 2/2] Silence runtime complaints on platform devices To: Eric Anholt Cc: ML dri-devel , "Linux-Kernel@Vger. Kernel. Org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 630 Lines: 16 On 21 October 2016 at 18:12, Eric Anholt wrote: > glxgears was spamming this 12 times at startup because of Mesa's > probing of the DRM device code, which doesn't support platform > devices. > Better option is to add support for platform devices. Can we get anyone interested in that ? If we drop (the annoying) printf people will just ignore/forget about it, and things will fall through the cracks - similar to the 5+ pokes (at various people) to add support. On the cool side - it will allow you to use the DRI_PRIME/driconf's device_id=libudev_path_id_tag to manage the devices on your system. Thanks Emil