<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Drivers on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/drivers/</link><description>Recent content in Drivers on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sun, 26 Aug 2012 15:25:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/drivers/index.xml" rel="self" type="application/rss+xml"/><item><title>Tales Of A First Time Driver Developer</title><link>http://karpoke.ignaciocano.com/2012/08/26/tales-of-a-first-time-driver-developer/</link><pubDate>Sun, 26 Aug 2012 15:25:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/08/26/tales-of-a-first-time-driver-developer/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Since 2004, I’ve owned a ThinkPad A22m - a laptop that came out in
2001. Much to the dismay of certain friends, I still feel no need to
purchase a newer computer. I’ve often said that this old hardware can
do everything I need while still letting me run modern software.
However, it now seems like I will have to take some responsibility for
the code if I want that to still be true in the future.&lt;/p&gt;
&lt;p&gt;Specifically, I am talking about open source ATI drivers on GNU /
Linux. The four main video card lines released by ATI (now owned by
AMD) have been Wonder, Mach, Rage and Radeon. I don’t think Wonder
cards have any features that would warrant the development of a
dedicated driver but Linux drivers for the other three have been
written.&lt;/p&gt;
&lt;p&gt;The Radeon driver is actively maintained by software engineers at AMD
and some people who work for other software companies. The other two?
Not so much. The Rage 128 driver was especially in need of a major
update recently. And since my computer has a Rage Mobility graphics
card, I felt motivated to start working on the code even though I had
never hacked such a low-level piece of software before. Since the
effort has largely succeeded, I would like to share my experiences
with editing an open source video driver. The learning curve was quite
steep and when I first started reading documentation, it seemed like
it was written for a different audience. This post is going to be an
unadultered attempt to get a completely new reader to catch on to what
I did. I’m sure I will later find out that many things written in this
post are technically incorrect, but I will not edit them. I want the
only knowledge communicated in this piece to be the knowledge that one
might reasonably be expected to have after jumping into driver
development for the first time.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>