Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <f8e11d45-3803-47eb-4323-48efe36d102f@collabora.com>
Date:   Tue, 11 Apr 2023 11:01:12 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
Subject: Re: [PATCH 0/6] Initial Rust V4L2 support
To:     Willy Tarreau <w@1wt.eu>,
        Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc:     Hans Verkuil <hverkuil@xs4all.nl>, wedsonaf@gmail.com,
        ojeda@kernel.org, mchehab@kernel.org,
        rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-media@vger.kernel.org, kernel@collabora.com
References: <20230406215615.122099-1-daniel.almeida@collabora.com>
 <136035a4-26df-1c14-e51e-406b4ee5fe33@xs4all.nl>
 <CANiq72kzgopREcNcAnjCBk2u9b9cJ4f_jPix6LWYSkcOV5kubw@mail.gmail.com>
 <ZDVXbw/097jvjKvK@1wt.eu>
Content-Language: en-US
From:   Daniel Almeida <daniel.almeida@collabora.com>
In-Reply-To: <ZDVXbw/097jvjKvK@1wt.eu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hans (Verkuil),

> One potential solution is to have somebody step up as the maintainer
> of the Rust side (e.g. the author of the abstractions).

I'd be willing to step up as maintainer for the Rust V4L2 stuff. I will 
also be contributing more bindings if we decide that's worthwhile, 
because right now this is obviously very incomplete.

IIRC, Benjamin was originally looking into Rust for the AV1 driver he's 
just written in C, but back then there was just too much work to be done 
to even get started on the task. My point is that maybe these type of 
drivers - i.e.: m2m codec stuff - are good candidates for Rust, because 
the codec-specific bits are very self-contained.

-- Daniel