From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C88FB26B756; Tue, 3 Feb 2026 18:53:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770144804; cv=none; b=g3FTXo/OWiELt5OW9fABKn6gyOnVeSpZP0UOu8dVlmZ20wcfbAy4vz8a4yBGAQus8tthP1JHary/VhZ7mwS3knb6VkUPpNeDec4xRiZTMtKLfu4/yuF0PhemjB1WHgYZ1WXd6fjryyrkzXsKxd41ZItXtUCbuv6zg1mrLjFk8h4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770144804; c=relaxed/simple; bh=s4q+NiCRmoTLb6bCypTgN56XD7KPRRtIDidTskOTv2Q=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=vEIKKDdrkw0XHosh34pNKFW+PVc5KNdNrB7jWVwd2hF+yg4a8yi4Gd9ESz8uUpAJszgXJDmFEHAXB6LrhavLG9MaZnXn7rb52Gen324sxnQn5o2egm6+V5EvddOxweAbH6v6SuIyzKUp16OiGs+iaNt9hvtnUzlivhorRLBZBKk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=mt3lILHH; arc=none smtp.client-ip=192.198.163.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="mt3lILHH" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1770144803; x=1801680803; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=s4q+NiCRmoTLb6bCypTgN56XD7KPRRtIDidTskOTv2Q=; b=mt3lILHHAJbpLd1RZF7Cjen0vZk+pL0MbrHiDwLsj/See6j81RwHpA1g UXgc2fuslzelMKp86xAEvKU/kmycrBJ9CDEoFqBmHNK/8Ll0jdKwn965E xZwfCcccHrx/OoHocxFhBQJC1E4jc7qGUU/2KuoZT8FEXf+IeCcOHMVwG osnjg5DN+uLTTwKh6OAk8tvMoIXJrMhd8YsFB+e44BPTHeroTZJsOYGau SJa8x8rBa86t4LRzzHYeILcAN5XjvBqhswAs7JJSdzw5a0i0ts2gTHnXD CJt+hbCXRvXhAWTPJ42EYFVxRMUa7yNHbC8C1J/xLg1Sbvszo1cBVbcfe w==; X-CSE-ConnectionGUID: fvfMHq3WSGqBjpmBRvrJ0A== X-CSE-MsgGUID: /vZv2GqMT9etsU+yHbT5IQ== X-IronPort-AV: E=McAfee;i="6800,10657,11691"; a="81955315" X-IronPort-AV: E=Sophos;i="6.21,271,1763452800"; d="scan'208";a="81955315" Received: from orviesa003.jf.intel.com ([10.64.159.143]) by fmvoesa105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2026 10:53:22 -0800 X-CSE-ConnectionGUID: UpHXyacrTXmG80ZyL9F+Qw== X-CSE-MsgGUID: N1Mg281QTF63CW9wdle5fQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,271,1763452800"; d="scan'208";a="214084276" Received: from klitkey1-mobl1.ger.corp.intel.com (HELO localhost) ([10.245.246.205]) by ORVIESA003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2026 10:53:16 -0800 From: Jani Nikula To: johannes.goede@oss.qualcomm.com, Jarkko Sakkinen , linux-media@vger.kernel.org Cc: anisse@astier.eu, oleksandr@natalenko.name, linux-integrity@vger.kernel.org, Mauro Carvalho Chehab , Hans Verkuil , Laurent Pinchart , Sakari Ailus , Jacopo Mondi , Ricardo Ribalda , open list Subject: Re: [RFC PATCH v2] media: Virtual camera driver In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs Bertel Jungin Aukio 5, 02600 Espoo, Finland References: <20260202204425.2614054-1-jarkko@kernel.org> <6b192c71-c389-4a6e-b7c3-ddcd5cc4aa34@oss.qualcomm.com> <37a0d91c2e78c97f3d956444c4f7a2a2fca9ae06@intel.com> Date: Tue, 03 Feb 2026 20:53:13 +0200 Message-ID: <2bda02cb3da6cb6ca7dcf545a5b7af27fb7a6e37@intel.com> Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Tue, 03 Feb 2026, johannes.goede@oss.qualcomm.com wrote: > OTHO evdi: https://github.com/DisplayLink/evdi has been kept out > of the kernel for pretty much the same reasons by the drm/kms folks. > > At least AFAIK there still is no way to present virtual kms capable > display outputs backed by userspace in the kernel. > > I completely understand where you're coming from wrt v4l2-loopback > support (or something equivalent) but asking for this really is > the same as asking for the evdi driver to get merged, which AFAIK > has been blocked for the reason of avoiding proprietary userspace > display output drivers (I guess there might be technical reasons too). I'm not sure this is the same thing, though. The DRM subsystem does require an open source userspace for new uAPI, which is stricter than most subsystems [1]. Other than that, I don't think anyone's actively keeping evdi out of the kernel. AFAIK there hasn't been a serious attempt at upstreaming it either. Which is pretty much because there's no open userspace. Nobody's cared enough to either write one or open source the existing one for a decade [2]. BR, Jani. [1] https://docs.kernel.org/gpu/drm-uapi.html#open-source-userspace-requirements [2] https://github.com/DisplayLink/evdi/issues/25 -- Jani Nikula, Intel