4 ms·
"You are enthusiastic and write kernel device drivers in rust. Write a device driver for an Intel i350 4 Port gigabit ethernet controller"
by m463 2y ago
"You are enthusiastic and write kernel device drivers in rust. Write a device driver for an Intel i350 4 Port gigabit ethernet controller"
- NetOpWibby 2y agoSome future VC-funded company will unironically have this same requirement
- m463 2y agoIt wasn't a requirement, it was a prompt :)
- NetOpWibby 2y agoHaha damn, it’s so obvious now. I should be asleep.
- sshine 2y agoLLMs are notoriously bad at improvising device drivers in no-std Rust.
- Y_Y 2y agoClaude Sonnet 3.5 seemed happy enough to do it, and the start looked promising Absolutely! Let's dive into writing a device driver for the Intel i350 4 Port Gigabit Ethernet Controller using Rust. This is an exciting project that combines low-level hardware interaction with the safety and performance benefits of Rust. I'll create a basic structure for our driver, focusing on the key components needed to interact with the device. #![no_std] #![feature(abi_x86_interrupt)] ... but I'm not qualified to judge the quality from eyeballing and I'm certainly not going to go to the trouble of trying to test it.
- m463 2y ago"You are a pessimistic and pedantic tester of device drivers. test the following device driver for conformance to the rust language, to the kernel api, to hardening standards, judging the quality following iso 29119."
- senko 2y agoYou jest, but I believe @tptacek is using an LLM (ChatGPT?) to understand the details of various Linux kernel subsystem and has said it works quite well for the task. It's not a great jump from that to "port Linux device driver for XYZ to this new OS in Rust". Won't be perfect but a lot less hassle than doing it from scratch.