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
Should you trust an online service to store your online passwords?
New B+ board lets you build cool things without the complication of a powered USB hub.
Redmond rushes in to root out alleged malware haven.
New initiative will bring futuristic virtual reality effects to the web surfing experience.
Dyreza malware launches a man-in-the-middle attack that compromises SSL.
New cloud combines worldwide access with local attention to data security.
A first cousin of the recent Heartbleed attack affects EAP-based wireless and peer-to-peer authentication.
FOSS community acts to protect freedom of choice for laptop devices.
Quintessential open source browser shores up its market share with a step toward the proprietary dark side.
Authorities in 16 countries take action against users of the imfamous BlackShades malware tool.