Rust for Linux List
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Daniel Almeida <daniel.almeida@collabora.com>,
	Frederic Laing <frederic.laing.development@gmail.com>
Cc: a.hindborg@kernel.org, acourbot@nvidia.com,
	alex.gaynor@gmail.com, aliceryhl@google.com,
	bjorn3_gh@protonmail.com, boqun.feng@gmail.com, dakr@kernel.org,
	gary@garyguo.net, kernel@collabora.com,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	lossin@kernel.org, ojeda@kernel.org,
	rust-for-linux@vger.kernel.org, tmgross@umich.edu
Subject: Re: [PATCH 0/7] rust: add initial v4l2 support
Date: Thu, 18 Dec 2025 11:12:40 +0100	[thread overview]
Message-ID: <18f85697-358c-480c-89a0-8559f600f62d@kernel.org> (raw)
In-Reply-To: <73B8194B-4E21-4E5D-99AA-54CD273858B4@collabora.com>

On 17/12/2025 15:35, Daniel Almeida wrote:
> Hi Frederic,
> 
>> On 16 Dec 2025, at 14:03, Frederic Laing <frederic.laing.development@gmail.com> wrote:
>>
>> Hi all,
>>
>> I’m new to contributing to the kernel and was reading through this thread. I would like to ask about the current status of this patch set. Is anyone still actively working on it?
>>
>> If it’s unmaintained at the moment, I’d be happy to take over and work on addressing the review comments and resubmitting an updated version.
>>
>> In case you're wondering why I am interested; I am currently working on camera software that utilizes the Microsoft Kinect 360 and V2 camera variants. Luckily there is already `drivers/media/usb/gspca/kinect.c` but it has some errors (like reporting invalid frame rates for color data) and design flaws that makes it impossible to stream depth and color data from a single device at the same time. I already got a new user space driver working in rust and would like to upstream it to the kernel to replace the older kinect driver written in C.
>>
>> Thanks for your time,
>> Frederic Laing
> 
> I did not hear anything from the media people so far.
> 
> Mauro, Hans?

Speaking only for myself, there still isn't the time available for me at least
to support rust. We also need to get the multicommitter model started, which
is only pending on the documentation right now. That really should have been
done this year, and I really hope we can finish that early next year. We
need that up and running.

Basically the situation is unchanged from 2 (?) years ago: too much to do, not
enough time.

I don't see this changing for me for 2026.

Regards,

	Hans

      reply	other threads:[~2025-12-18 10:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  5:49 [PATCH 0/7] rust: add initial v4l2 support Daniel Almeida
2025-08-18  5:49 ` [PATCH 1/7] rust: media: add the media module Daniel Almeida
2025-08-18  8:56   ` Miguel Ojeda
2025-08-18 10:28   ` Janne Grunau
2025-08-18  5:49 ` [PATCH 2/7] rust: v4l2: add support for v4l2_device Daniel Almeida
2025-08-18  9:14   ` Danilo Krummrich
2025-08-18  5:49 ` [PATCH 3/7] rust: v4l2: add support for video device nodes Daniel Almeida
2025-08-18  9:26   ` Danilo Krummrich
2025-08-18  5:49 ` [PATCH 4/7] rust: v4l2: add support for v4l2 file handles Daniel Almeida
2025-08-18  5:49 ` [PATCH 5/7] rust: v4l2: add device capabilities Daniel Almeida
2025-08-20  4:14   ` Elle Rhumsaa
2025-08-18  5:49 ` [PATCH 6/7] rust: v4l2: add basic ioctl support Daniel Almeida
2025-08-20  4:22   ` Elle Rhumsaa
2025-08-18  5:49 ` [PATCH 7/7] rust: samples: add the v4l2 sample driver Daniel Almeida
2025-08-20  4:24   ` Elle Rhumsaa
2025-08-20 12:39   ` Danilo Krummrich
2025-08-18  8:45 ` [PATCH 0/7] rust: add initial v4l2 support Miguel Ojeda
2025-12-16 17:03 ` Frederic Laing
2025-12-17 14:35   ` Daniel Almeida
2025-12-18 10:12     ` Hans Verkuil [this message]

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=18f85697-358c-480c-89a0-8559f600f62d@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=frederic.laing.development@gmail.com \
    --cc=gary@garyguo.net \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /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