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;
References: <a68fca00-666a-bbf4-b4d3-acd409dd69d2@gmail.com>
User-agent: mu4e 1.10.3; emacs 28.2.50
From:   Andreas Hindborg <nmi@metaspace.dk>
To:     Ryo Munakata <ryomnktml@gmail.com>
Cc:     rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
        FUJITA Tomonori <fujita.tomonori@gmail.com>
Subject: Re: Rust ENC28J60 ethernet driver working on Raspberry Pi
Date:   Fri, 12 May 2023 19:28:09 +0200
In-reply-to: <a68fca00-666a-bbf4-b4d3-acd409dd69d2@gmail.com>
Message-ID: <87mt29e9vb.fsf@metaspace.dk>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk


Ryo Munakata <ryomnktml@gmail.com> writes:

> Hi all,
>
> I've written an ethernet driver for ENC28J60, a stand-alone ethernet controller
> with a SPI interface, in Rust.
> It works fine on Raspberry Pi 4B with Raspbian AArch64.
> You can connect to the internet and play some videos on YouTube with it
> (10BASE-T though).
> I hope it will be an example of real-world drivers in Rust.
>
> * ENC28J60 ethernet driver in Rust
> enc28j60rs: https://github.com/pfpacket/enc28j60rs
> `impl Sync/Send`, mostly because of raw pointers, and the initialization of
> `workqueue::Work` and `sync::Spinlock`
> require a tiny bit of "unsafe" code, but otherwise no unsafe code used.
>
> * The forked kernel with Rust support for SPI and netdev
> https://github.com/pfpacket/linux-rpi-rust/tree/rust-netdev
> Forked from the Raspberry Pi tree and merged Rust-for-Linux `rust` branch into
> it.
> (BTW are there any easier way to get Rust-for-Linux work on Raspberry Pi? If so
> please let me know.)
> Then I added the SPI support referencing rust/kernel/platform.rs and netdev
> support.
> The netdev support is based on the following GitHub PR from Fujita-san:
> https://github.com/Rust-for-Linux/linux/pull/908

This is cool, thanks! I will check it out at some point.

Best regards
Andreas Hindborg