[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56777298b3883fc2b105af52be80cf5f0cf14be0.camel@collabora.com>
Date: Wed, 03 May 2023 08:00:40 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Asahi Lina <lina@...hilina.net>
Cc: Nicolas Dufresne <nicolas.dufresne@...labora.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Hans Verkuil <hverkuil@...all.nl>, wedsonaf@...il.com,
ojeda@...nel.org, mchehab@...nel.org,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, kernel@...labora.com,
Sakari Ailus <sakari.ailus@....fi>,
Antoni Boucher <bouanto@...o.com>
Subject: Re: [PATCH 0/6] Initial Rust V4L2 support
Hi Lina, all,
I disagree that we need to wait for anything as a precondition for
writing the things Nicolas listed. The reason being that he listed out
some very self-contained codebases. These would not depend on the
kernel crate either for the most part (or at all, even, but going from
memory here..).
Note that the codec library in particular would rarely be touched after
it's written, as the algorithms in there are more or less "set in
stone" by the codec specs.
Maintaining these until they can be merged would be essentially free,
unless I am missing something?
-- Daniel
Powered by blists - more mailing lists