Teaching how to write device drivers
maddog considers the benefits of teaching students how to write device drivers.
Recently, I was working with an “upstream” developer of Linux kernel device drivers. This particular developer was working in the media subsystem section of the kernel, where there are a LOT of device drivers because the media subsystem is either the second or third largest driver subsystem in the kernel. The developer reviewed about 3,000 patches per kernel cycle in addition to doing about 100 patches per kernel cycle himself. He was not complaining, just letting me know the work load.
In the midst of our discussions, he lamented:
Not actually knowing why Academia doesn’t contribute upstream, I would guess that writing a new driver is probably a too short project for them, as students are supposed to work on a 6-month to 2-year window, while writing a new driver takes only a few days with the proper datasheets and/ or a reference driver and a knowledgeable developer.
Buy this article as PDF
Lennart Poettering wants to change the way Linux developers talk to each other.
Enterprise giant frees itself from ink and home PCs (and visa versa).
Mozilla’s product think tank sinks silently into history.
TODO group will focus on open source tools in large-scale environments.
New tool will look like GParted but support a wider range of storage technologies.
New public key pinning feature will help prevent man-in-the-middle attacks.
Carnegie Mellon researchers say 3 million pages could fall down the phishing hole in the next year.
The US government rolls new best-practice rules for protecting SSH.
Klaus Knopper announces the latest version of his iconic Live Linux system.
All websites that use these popular CMS tools could be vulnerable to denial of service attacks if users don't install the updates.