<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Rainbow Dash Network</provider_name>
 <provider_url>http://rainbowdash.net/</provider_url>
 <title>Jon and Angela Conrad (fnordly)'s status on Sunday, 21-Aug-11 19:54:28 UTC</title>
 <author_name>Jon and Angela Conrad (fnordly)</author_name>
 <author_url>http://rainbowdash.net/fnordly</author_url>
 <url>http://rainbowdash.net/notice/419252</url>
 <html>@&lt;span class=&quot;vcard&quot;&gt;&lt;a href=&quot;http://rainbowdash.net/user/250&quot; class=&quot;url&quot; title=&quot;&amp;#x2605;&quot;&gt;&lt;span class=&quot;fn nickname&quot;&gt;starshine&lt;/span&gt;&lt;/a&gt;&lt;/span&gt; Have you ever hacked at a device driver module for Linux? It is actually kind of fun, because everyone that has ever written one has just followed a skeleton structure of a preexisting module. They are all alike and all different and all varying sizes and amounts of complexity and simplicity at the same time. In other words: the source for the device driver is likely to be the most straight-forward part of your kernel for you to just jump into and experiment with... Unless you don't compile the kernel yourself. In that case, I don't know if this would help.</html>
</oembed>
