From: "Danilo Krummrich" <dakr@kernel.org>
To: "Daniel Almeida" <daniel.almeida@collabora.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Michal Wilczynski" <m.wilczynski@samsung.com>,
"Igor Korotin" <igor.korotin.linux@gmail.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/2] samples: rust: add a USB driver sample
Date: Sat, 06 Sep 2025 17:22:40 +0200 [thread overview]
Message-ID: <DCLTJMIAMCVL.35U236MMS5CCK@kernel.org> (raw)
In-Reply-To: <9657C897-087E-4544-849B-964E99D95A50@collabora.com>
On Sat Sep 6, 2025 at 4:50 PM CEST, Daniel Almeida wrote:
> So far I see a pattern where sample drivers count as users. This has been the
> case, for example, for rust_dma.rs. I was under the impression that the same
> would apply here. Although I do realize that there were plans for dma code
> other than rust_dma.rs, of course.
This isn't the case, we have those sample drivers to make it easy to review the
the code and illustrate in an isolated context how it works. But, there has
always been a "real" user behind that. In the case of the DMA work it was Nova.
> As for Nova and Tyr, these are projects with a lot of big companies involved.
>
> They were able to break this chicken and egg situation in part due to that,
> because companies were willing to allocate engineers for both the drivers _and_
> the required infrastructure. Unless the same can be said for USB, media or any
> other subsystems, I don't see it happening.
Well, this is true for Nova and Tyr, but I disagree that this is the reason we
were able to break the chicken and egg problem.
For instance, the initial lift around the driver core, PCI, I/O, etc.
infrastructure was done by me, a single person. This could have been happening
in the context of a very simple and small driver as well, rather than a big GPU
driver with lots of companies and people involved.
Igor (Cc) is doing the initial lift for I2C and Michal (Cc) for PWM for
instance.
So, I see those things happen and I don't think that such initial lifting
necessarily needs big companies with dozens of engineers being involved.
If we know people who want to write drivers for a subsystem that doesn't yet
have Rust infrastructure (such as USB), let's encourage them to get started /
involved anyways and let's help them as they go.
But also please don't get me wrong, I understand and very much appreciate you
want to get the ball rolling, but let's not discourage people by making it
sounds as if it would be impossible for individuals.
next prev parent reply other threads:[~2025-09-06 15:22 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 18:18 [PATCH 0/2] rust: usb: add initial USB abstractions Daniel Almeida
2025-08-25 18:18 ` [PATCH 1/2] rust: usb: add basic " Daniel Almeida
2025-08-25 20:49 ` Benno Lossin
2025-08-25 21:03 ` Daniel Almeida
2025-09-23 13:21 ` Danilo Krummrich
2025-09-23 13:31 ` Daniel Almeida
2025-09-23 14:03 ` Danilo Krummrich
2025-09-23 14:30 ` Greg Kroah-Hartman
2025-09-23 14:38 ` Danilo Krummrich
2025-09-23 14:52 ` Greg Kroah-Hartman
2025-09-23 15:06 ` Danilo Krummrich
2025-09-23 14:58 ` Alan Stern
2025-09-23 14:13 ` Greg Kroah-Hartman
2025-09-23 14:16 ` Oliver Neukum
2025-09-23 14:22 ` Greg Kroah-Hartman
2025-09-23 14:25 ` Danilo Krummrich
2025-09-23 14:37 ` Greg Kroah-Hartman
2025-09-23 14:42 ` Danilo Krummrich
2025-09-23 14:49 ` Greg Kroah-Hartman
2025-09-23 15:46 ` Danilo Krummrich
2025-09-23 14:18 ` Danilo Krummrich
2025-08-25 18:18 ` [PATCH 2/2] samples: rust: add a USB driver sample Daniel Almeida
2025-09-06 11:14 ` Greg Kroah-Hartman
2025-09-06 12:04 ` Daniel Almeida
2025-09-06 12:10 ` Greg Kroah-Hartman
2025-09-06 12:41 ` Daniel Almeida
2025-09-06 13:07 ` Greg Kroah-Hartman
2025-09-06 14:49 ` Alan Stern
2025-09-06 14:56 ` Daniel Almeida
2025-09-06 13:22 ` Danilo Krummrich
2025-09-06 14:50 ` Daniel Almeida
2025-09-06 15:22 ` Danilo Krummrich [this message]
2025-09-06 15:46 ` Daniel Almeida
2025-09-06 15:48 ` Danilo Krummrich
2025-09-09 11:19 ` Simon Neuenhausen
2025-09-09 12:12 ` Daniel Almeida
2025-09-09 13:25 ` Greg Kroah-Hartman
2025-09-09 12:14 ` Greg Kroah-Hartman
2025-09-09 13:05 ` Simon Neuenhausen
2025-08-25 20:32 ` [PATCH 0/2] rust: usb: add initial USB abstractions Greg Kroah-Hartman
2025-09-23 12:05 ` Greg Kroah-Hartman
2025-09-23 12:29 ` Alice Ryhl
2025-09-23 12:31 ` Greg Kroah-Hartman
2025-09-23 12:34 ` Daniel Almeida
2025-09-23 12:41 ` Greg Kroah-Hartman
2025-09-23 12:55 ` Miguel Ojeda
2025-09-23 12:56 ` Miguel Ojeda
2025-09-23 13:24 ` Daniel Almeida
2025-09-23 21:29 ` Miguel Ojeda
2025-09-25 12:52 ` Greg Kroah-Hartman
2025-09-25 12:58 ` Daniel Almeida
2025-09-25 13:29 ` Danilo Krummrich
2025-09-25 17:38 ` Greg Kroah-Hartman
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=DCLTJMIAMCVL.35U236MMS5CCK@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=igor.korotin.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=m.wilczynski@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.