Re: RfL branch for PCI bindings

[Andreas Hindborg <a.hindborg@samsung.com>]

Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes:

> On Thu, Feb 1, 2024 at 4:02 PM Danilo Krummrich <dakr@redhat.com> wrote:
>>
>> I'd like to come back to our discussion from the last "Rust for DRM" meeting regarding a
>> common "rust-pci" branch.
>>
>> As discussed, in the context of the Nova project we are interested in using those bindings,
>> contribute some more (also in the context of Philipp's recent PCI work) and help moving the
>> code upstream.
>>
>> With Nova we should have a driver project which should justify further efforts to upstream
>> the code.
>
> Thanks Danilo!
>
> My understanding from the meeting was that Andreas kindly agreed to
> maintain a `rust-pci` branch in a compilable state (i.e. rebasing it
> on top of e.g. `rust-next`). I am happy to create the branch already
> if Andreas is ready, add it to the website, etc.
>
> Or if you (Danilo) prefer to drive the branch instead (e.g. because
> you may have more bandwidth), that is also fine.

Exactly. I am currently keeping the patches alive for the Rust NVMe
driver that lives here [1], latest rebase here [2].

I am not the original author of the Rust PCI patches. As far as I know,
no one else is maintaining a copy of these patches on top of mainline
(if there was, I would just use their work).

I volunteer to extract these patches from the nvme tree into a separate
pci tree and keep that rebased on mainline + accept fixes and features
into that tree.

We can also do it the other way round and I would just rebase nvme on
top of your pci tree, that is up to you.

I don't have any plans of sending these patches upstream for now, since
the NVMe driver is not welcome upstream. If/when Nova or another Rust
project depending on pci is ready to merge, I would be happy to help
upstream the pci patches, if that makes sense. Again, you could also do
it yourself, that is completely up to you. Or perhaps the original
authors are interested in helping with this - I do not know since it
never came up.

We could start out in one configuration and then change later down the
road if it becomes clear that another config would be more beneficial.

Best regards,
Andreas


[1] https://rust-for-linux.com/nvme-driver
[2] https://github.com/metaspace/linux/commits/nvme-6.7/