/tech/ - Technology★

Always thank the bus driver

I write drivers, last time I answered questions people here bitched at me for not spoonfeeding them harder. This taught me an important lesson, the only way to learn to write drivers is the hard way, git gud by reading source code or kill yourselves.

drivers are a sekrit club.

Use >>995744 (checked) as an example. Much like kernel devs, driver devs are generally 'C purists', except driver devs are more comfy with 'evil hardware tricks' that piss off the rival kernel devs. Both expect you push through the pain to reach glory, or quit trying. Driver devs only know how drivers work when they are stable, kernel devs only know how drivers work when drivers are buggy.

Drivers can be made in vi, emacs, sublimetext, eclipse, nano, or even ed, the standard text editor.

Here's an intro for OpenBSD drivers:

https://www.youtube.com/watch?v=W5qhWw07qpU

The PDF is here:

https://www.openbsd.org/papers/eurobsdcon2017-device-drivers.pdf

>>995733 (OP)

>Drivers, what are they?

People operating certain kinds of vehicle. Driving something makes you a driver.