←back to thread

309 points LorenDB | 1 comments | | HN request time: 0s | source
Show context
Santosh83 ◴[] No.42637177[source]
Read somewhere that it is relatively easy to adapt NetBSD's drivers into a custom kernel... maybe Serenity folks can go that way? Device drivers are huge obstacle for any fledgling OS.
replies(6): >>42637487 #>>42638178 #>>42638309 #>>42639168 #>>42642231 #>>42665209 #
mysterydip ◴[] No.42637487[source]
> Device drivers are a huge obstacle for any fledgling OS.

I've wondered if new/hobby OSes would fare better by starting out targeting a popular single board computer like a raspberry pi? A mostly fixed set of hardware to make/get drivers for and test your system on.

replies(6): >>42637523 #>>42638258 #>>42639203 #>>42639284 #>>42639368 #>>42646433 #
yjftsjthsd-h ◴[] No.42637523[source]
I've also argued in favor of that; I don't actually like Pis personally, but they're a super common, cheap enough, easy to acquire system and that's huge.
replies(1): >>42637995 #
FuriouslyAdrift ◴[] No.42637995[source]
Raspberry Pi's are highly proprietary for hardware blobs...
replies(5): >>42638061 #>>42638095 #>>42638097 #>>42638150 #>>42638235 #
1. fngjdflmdflg ◴[] No.42638235{3}[source]
I think the replies to this post may be missing the point? AIUI The raspi CPU drivers being closed makes it actually pretty hard to write an open driver for it. So you would need raspberry pi or their CPU supplier to write the driver for you, which they wouldn't do for a small OS. It took multiple years to support raspi 4 in mainline Linux and AFAIK raspi 5 still does not have a fully functioning mainline driver. That's why Raspberry Pi OS exists. You would pick a CPU that has open drivers because it would be easier to write your own for a different operating system.