dri-devel Archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Naushir Patuck <naush@raspberrypi.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org,
	libcamera-devel@lists.libcamera.org
Subject: Re: [PATCH 2/2] drm/fourcc.h: Add libcamera to Open Source Waiver
Date: Thu, 9 May 2024 12:18:04 +0200	[thread overview]
Message-ID: <Zjyi3CFNIKFv1HG5@phenom.ffwll.local> (raw)
In-Reply-To: <20240228102245.80469-3-jacopo.mondi@ideasonboard.com>

On Wed, Feb 28, 2024 at 11:22:44AM +0100, Jacopo Mondi wrote:
> The libcamera (www.libcamera.org) project uses the drm/fourcc.h header
> to define its own image formats. Albeit libcamera aims for fully open
> source driver and userspace software stacks, it is licensed with the
> 'GNU L-GPL' license which allows closed source application to link
> against the library.
> 
> Add libcamera to the list projects to which the 'Open Source User
> Waiver' notice applies.
> 
> Signed-off-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> ---
>  include/uapi/drm/drm_fourcc.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h
> index 4e6df826946a..beef743ac818 100644
> --- a/include/uapi/drm/drm_fourcc.h
> +++ b/include/uapi/drm/drm_fourcc.h
> @@ -97,6 +97,7 @@ extern "C" {
>   *
>   * - GL
>   * - Vulkan extensions
> + * - libcamera

I think we can bikeshed whether we want to be more specific (with like
listing the gl/vk extensions), but imo it's a good start and imo also
totally makes sense to officially list libcamera. On both patches.

Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

I think collect a handful more acks from drm and libcamera folks and then
land this.
-Sima

>   *
>   * and other standards, and hence used both by open source and closed source
>   * driver stacks, the usual requirement for an upstream in-kernel or open source
> -- 
> 2.43.2
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2024-05-09 10:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 10:22 [PATCH 0/2] drm/fourcc.h: Add libcamera to Open Source Waiver Jacopo Mondi
2024-02-28 10:22 ` [PATCH 1/2] drm/fourcc.h: List of Open Source Waiver projects Jacopo Mondi
2024-02-28 10:22 ` [PATCH 2/2] drm/fourcc.h: Add libcamera to Open Source Waiver Jacopo Mondi
2024-05-09 10:18   ` Daniel Vetter [this message]
2024-03-14 10:12 ` [PATCH 0/2] " Jacopo Mondi
2024-03-26 17:54   ` Kieran Bingham
2024-05-09 10:20   ` Daniel Stone

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zjyi3CFNIKFv1HG5@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=libcamera-devel@lists.libcamera.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=naush@raspberrypi.com \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).