[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <18f85697-358c-480c-89a0-8559f600f62d@kernel.org>
Date: Thu, 18 Dec 2025 11:12:40 +0100
From: Hans Verkuil <hverkuil+cisco@...nel.org>
To: Daniel Almeida <daniel.almeida@...labora.com>,
Frederic Laing <frederic.laing.development@...il.com>
Cc: a.hindborg@...nel.org, acourbot@...dia.com, alex.gaynor@...il.com,
aliceryhl@...gle.com, bjorn3_gh@...tonmail.com, boqun.feng@...il.com,
dakr@...nel.org, gary@...yguo.net, kernel@...labora.com,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
lossin@...nel.org, ojeda@...nel.org, rust-for-linux@...r.kernel.org,
tmgross@...ch.edu
Subject: Re: [PATCH 0/7] rust: add initial v4l2 support
On 17/12/2025 15:35, Daniel Almeida wrote:
> Hi Frederic,
>
>> On 16 Dec 2025, at 14:03, Frederic Laing <frederic.laing.development@...il.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
Powered by blists - more mailing lists