From: Geert Stappers <stappers@stappers.nl>
To: Alex Gaynor <alex.gaynor@gmail.com>,
FUJITA Tomonori <tomo@exabit.dev>,
rust-for-linux@vger.kernel.org
Subject: Re: Rust e1000 driver (Intel Ethernet adapter)
Date: Wed, 28 Sep 2022 16:31:21 +0200 [thread overview]
Message-ID: <20220928143120.iavijwru6r3qnhiy@gpm.stappers.nl> (raw)
In-Reply-To: <CAFRnB2U9EBdRLy0YCdQjCvgHra4T9bB+hrW==5iGWNhS-U7MUQ@mail.gmail.com>
On Sun, Sep 18, 2022 at 09:59:02PM -0400, Alex Gaynor wrote:
> On Sun, Sep 18, 2022 at 9:57 PM FUJITA Tomonori <tomo@exabit.dev> wrote:
> >
> > Hi,
> >
> > I've implemented Rust e1000 driver (Intel Ethernet adapter):
> >
> > https://github.com/fujita/rust-e1000
> >
> > There are many places to use the C bindings directly for now. I try to
> > clean up and push abstractions for NIC drivers (DMA, PCI, network,
> > etc).
> >
> > I can ping on QEMU. Needs a bit more work for real hardware.
> >
> > Thanks,
>
> That's great to see. Thanks for your work on this and looking forward
> to seeing the pull requests!
>
Where to look for such merge request?
Long version of my question:
I can't tell how many hurdles there will be
nor how large (time consuming) the hurdles will be
for:
* git clone a modified version of a modified version of Linux kernel
* git clone the rust-e1000 at the right place
* build "rust for linux"
* start qemu with correct parameters
* find out that existing e1000 driver is NOT in the way
* see it working myself
Myself and probably others nearby the swimming pool
not knowning how nice the swimming water is.
Groeten
Geert Stappers
--
Silence is hard to parse
next prev parent reply other threads:[~2022-09-28 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 1:38 Rust e1000 driver (Intel Ethernet adapter) FUJITA Tomonori
2022-09-19 1:59 ` Alex Gaynor
2022-09-28 14:31 ` Geert Stappers [this message]
2022-09-28 15:24 ` Miguel Ojeda
2022-09-28 16:35 ` Geert Stappers
2022-09-28 16:46 ` Miguel Ojeda
2022-09-29 6:36 ` FUJITA Tomonori
2022-09-29 6:57 ` FUJITA Tomonori
2022-10-23 7:06 ` FUJITA Tomonori
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=20220928143120.iavijwru6r3qnhiy@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=alex.gaynor@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tomo@exabit.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).