<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>Linux Kernel — Jürgen Kreileder</title>
	<atom:link href="/articles/category/linux/linux-kernel/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Software Engineer and Consultant</description>
	<lastBuildDate>Sat, 29 Oct 2016 01:51:03 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">5303222</site><image><title>Jürgen Kreileder</title><url>/jk-rss.jpg</url><link>/</link><width>144</width><height>114</height><description>Software Engineer and Consultant</description></image>	<item>
		<title>LVM Snapshots With Debian Sarge and Linux 2.6.16</title>
		<link>/articles/lvm-snapshots-with-debian-sarge-and-linux-2616/</link>
					<comments>/articles/lvm-snapshots-with-debian-sarge-and-linux-2616/#comments</comments>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Sun, 09 Apr 2006 17:53:58 +0000</pubDate>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2006/04/09/lvm-snapshots-with-debian-sarge-and-linux-2616/</guid>

					<description><![CDATA[I have upgraded this server to kernel 2.6.16.2. The next backup cycle resulted in a minor disaster: The backup process deadlocked at removing the first LVM2 snapshot and the snapshot source volumes were blocking write accesses. A cleanup shutdown was impossible and I had to hard-reset the machine. After some searching I found out that<br />[&#8594; <a href="/articles/lvm-snapshots-with-debian-sarge-and-linux-2616/" class="more-link">Read the rest of this entry</a>]]]></description>
										<content:encoded><![CDATA[<p>I have upgraded this server to kernel 2.6.16.2. The next backup cycle resulted in a minor disaster: The backup process deadlocked at removing the first <a href="http://sources.redhat.com/lvm2/">LVM2</a> snapshot and the snapshot source volumes were blocking write accesses. A cleanup shutdown was impossible and I had to hard-reset the machine.</p>
<p>After some searching I found out that you <a href="http://www.ussg.iu.edu/hypermail/linux/kernel/0601.2/2055.html">apparently</a> need lvm2 2.02.01 or later and devmapper 1.02.02 or later to successfully remove snapshot volumes now. Unfortunately neither of these versions is available for sarge from Debian or <a href="http://backports.org/">backports.org</a> yet, so I had to make my own backports.<br />
As it turned out (see below), it is also necessary to use 2.6.16.12 or to apply the patch from this <a href="http://lkml.org/lkml/2006/4/20/261">email</a> to older 2.6.16 versions in order to reliably remove snapshots.</p>
<p>If you are brave enough, you can get the backported packages by adding</p>
<pre>deb http://blog.blackdown.de/static/debian/lvm/ sarge main
deb-src http://blog.blackdown.de/static/debian/lvm/ sarge main</pre>
<p>to <code>/etc/apt/sources.list</code>.</p>
<p>The repository contains debs for devmapper, dlm, lvm2, and lvm-common. The <code>Release</code> files is signed with my GPG <a href="/static/gpg.asc">key</a>. If you have a recent <code>apt</code> version, you can authenticate the packages after importing the key with <code>apt-key</code>:</p>
<pre>wget http://blog.blackdown.de/static/gpg.asc -O - | &#92;
    sudo apt-key add -</pre>
<p><em><strong>April 15th, 2006:</strong> In about 40 backup cycles I&#8217;ve <a href="http://www.ussg.iu.edu/hypermail/linux/kernel/0604.1/1643.html">seen</a> three lockups with 2.6.16.2 now. Until snapshots get fixed in 2.6.16, I&#8217;d recommend to stay with 2.6.15. I&#8217;m using 2.6.15.3 again now.</em></p>
<p><em><strong>April 24th, 2006:</strong> Added note about &#8220;<a href="http://lkml.org/lkml/2006/4/20/261">dm snapshot: fix kcopyd destructor</a>&#8221; patch from Alasdair G Kergon. With this patch snapshots work fine for me again.</em></p>
<p><em><strong>May 2nd, 2006:</strong> Alasdair G Kergon&#8217;s patch has been included in 2.6.16.12.</em></p>
]]></content:encoded>
					
					<wfw:commentRss>/articles/lvm-snapshots-with-debian-sarge-and-linux-2616/feed/</wfw:commentRss>
			<slash:comments>13</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">45</post-id>	</item>
		<item>
		<title>Debian Installer With Kernel 2.6.11</title>
		<link>/articles/debian-installer-with-kernel-2611/</link>
					<comments>/articles/debian-installer-with-kernel-2611/#comments</comments>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Sun, 26 Jun 2005 09:43:04 +0000</pubDate>
				<category><![CDATA[Config]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/06/26/debian-installer-with-kernel-2611/</guid>

					<description><![CDATA[As mentioned recently, Debian Sarge&#8217;s installer doesn&#8217;t work on my Dell Inspiron 9300. I like Debian but I think it&#8217;s a shame that the sarge installer was already outdated on the day of its release. The official sarge installer still uses a 2.4 kernel by default but includes a 2.6 kernel that can be used<br />[&#8594; <a href="/articles/debian-installer-with-kernel-2611/" class="more-link">Read the rest of this entry</a>]]]></description>
										<content:encoded><![CDATA[<p>As <a href="/2005/06/06/the-sky-is-falling/">mentioned</a> recently, <a href="http://debian.org/">Debian</a> Sarge&#8217;s installer doesn&#8217;t work on my Dell Inspiron 9300. I like Debian but I think it&#8217;s a shame that the sarge installer was already outdated on the day of its release.</p>
<p>The official sarge installer still uses a 2.4 kernel by default but includes a 2.6 kernel that can be used by booting with &quot;<code>install26</code>&quot; or &quot;<code>expert26</code>&quot;.  But even that kernel, 2.6.8, is too old for the Inspiron 9300. It still doesn&#8217;t recognize the hard disk.</p>
<p>Ubuntu&#8217;s installer, which uses a 2.6.11 kernel, works fine on the machine. Although <a href="http://ubuntu.com/">Ubuntu</a> is a nice distribution, I like pure Debian better. Unfortunately I wasn&#8217;t able to find any 2.6.11 based Debian installer on the net, even a question on <a href="http://lists.debian.org/debian-boot/">debian-boot</a> yielded nothing.</p>
<p>Anyhow, I finally had the time to build one myself:<br />
<a href="/static/debian/debian-2.6.11-i386-businesscard.iso">debian-2.6.11-i386-businesscard.iso</a> (<a href="/static/debian/debian-2.6.11-i386-businesscard.iso.sign">GPG signature</a>)</p>
<p>The image is basically a sarge businesscard ISO with a 2.6.11 kernel from Debian testing instead of the original 2.6.8 kernel.</p>
<p>Unlike with Ubuntu, installation on the Inspiron 9300 still doesn&#8217;t work out of the box but with a few tricks I was able to install Debian sarge:</p>
<ul>
<li>Boot with <code>expert26</code></li>
<li>When the installer starts up, switch to the second console (Alt-F2) and enter these commands:
<pre>
~ # modprobe ide_generic
~ # modprobe ata_piix</pre>
<p>Without this the installer won&#8217;t find the CD-ROM.</p>
</li>
<li>If network configuration via DHCP fails, just retry &#8212; worked for me</li>
<li>When asked what version of Debian you would like to install, choose <em>stable</em>.  Installing <em>testing</em> or <em>unstable</em> directly doesn&#8217;t work.</li>
<li>It doesn&#8217;t matter which kernel you choose to install, we have to replace it with a 2.6.11 kernel later anyway</li>
<li>Just before the first reboot, that means right after the installer ejects the CD-ROM, switch back to console two. Now download and install the latest available Debian kernel. I&#8217;ve used <a href="/static/debian/kernel-image-2.6.11-1-686_2.6.11-7_i386.deb">2.6.11-1-686</a>:
<pre style="overflow:auto;width:100%;">~ # mount -t proc proc /target/proc
~ # chroot /target
sh-2.05b# cd /root
sh-2.05b# wget http://blog.blackdown.de/static/debian/kernel-image-2.6.11-1-686_2.6.11-7_i386.deb
sh-2.05b# dpkg -i kernel-image-2.6.11-1-686_2.6.11-7_i386.deb
&hellip;
sh-2.05b# exit
~ # umount /target/proc</pre>
</li>
<li>Reboot (using the kernel just installed) and complete the installation</li>
<li>Upgrade to <em>testing</em> or <em>unstable</em></li>
<li>Build a custom kernel (2.6.12 or newer). It&#8217;s probably a good idea to include some additional libata <a href="http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/">patches</a>. To get the DVD drive working you have to apply this <a href="/static/kernel/ata-atapi.patch">patch</a>.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>/articles/debian-installer-with-kernel-2611/feed/</wfw:commentRss>
			<slash:comments>22</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">35</post-id>	</item>
		<item>
		<title>Fixing the ipt_recent Netfilter Module</title>
		<link>/articles/fixing-the-ipt_recent-netfilter-module/</link>
					<comments>/articles/fixing-the-ipt_recent-netfilter-module/#comments</comments>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Mon, 09 May 2005 14:52:59 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<category><![CDATA[Security]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/05/09/fixing-the-ipt_recent-netfilter-module/</guid>

					<description><![CDATA[I have experienced some strange behavior with my ipt_recent netfilter rules after an uptime of about 25 days. The rules started to block much too early. After rebooting the machine I was able to reproduce the problem for five minutes. This clearly indicated a problem with jiffies (Linux initialized jiffies so that the first roll-over<br />[&#8594; <a href="/articles/fixing-the-ipt_recent-netfilter-module/" class="more-link">Read the rest of this entry</a>]]]></description>
										<content:encoded><![CDATA[<p>I have experienced some strange behavior with my ipt_recent netfilter <a href="/2005/02/18/mitigating-ssh-brute-force-attacks-with-ipt_recent/">rules</a> after an uptime of about 25 days. The rules started to block much too early. After rebooting the machine I was able to reproduce the problem for five minutes. This clearly indicated a problem with jiffies (Linux initialized jiffies so that the first roll-over happens five minutes after booting).</p>
<p>A closer look at ipt_recent.c revealed that the time tests did not work like intended if one of the last hits was more than <code>LONG_MAX</code> jiffies ago or if the list of last hits contained empty slots and jiffies is greater than <code>LONG_MAX</code>.</p>
<p>To fix this, I replaced <em>jiffies</em> with <em>seconds since &#8217;00:00:00 1970-01-01 UTC&#8217;</em>. I have sent the <a href="/static/kernel/ipt_recent-fix.patch">patch</a> to linux-kernel and netfilter-devel. The patch also includes some 64-bit fixes.</p>
<p><em><strong>May 12th, 2005:</strong> The patch has been added to Linux 2.6.12-rc4-mm1</em></p>
<p><em><strong>September 8th, 2005:</strong> Please note that only the 64-bit parts of my patch have made it into 2.6.12. I&#8217;m working on an updated fix for the time comparison problems which will hopefully get accepted for 2.6.14 or later.</em></p>
<p><em><strong>September 12th, 2005:</strong> These issues have CAN numbers now: <a href="http://nvd.nist.gov/nvd.cfm?cvename=CAN-2005-2872">CAN-2005-2872</a> and <a href="http://nvd.nist.gov/nvd.cfm?cvename=CAN-2005-2873">CAN-2005-2873</a> (which supersede <a href="http://nvd.nist.gov/nvd.cfm?cvename=CAN-2005-2802">CAN-2005-2802</a>)</em></p>
<p><em><strong>July 10th, 2006:</strong> The jiffies issue is fixed in the vanilla kernel now.  Also note that 2.6.18 will contain a rewrite of ipt_recent.c.</em></p>
]]></content:encoded>
					
					<wfw:commentRss>/articles/fixing-the-ipt_recent-netfilter-module/feed/</wfw:commentRss>
			<slash:comments>50</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">27</post-id>	</item>
		<item>
		<title>2.6.12-rc-mm Lockups Fixed</title>
		<link>/articles/2612-rc-mm-lockups-fixed/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Tue, 03 May 2005 01:48:15 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/05/03/2612-rc-mm-lockups-fixed/</guid>

					<description><![CDATA[The lockups I have experienced with 2.6.12-rc-mm kernels have finally been fixed by this patch from Oleg Nesterov.]]></description>
										<content:encoded><![CDATA[<p>The <a href="/2005/04/19/lockups-with-2612-rc-mm-on-ppc64/">lockups</a> I have experienced with 2.6.12-rc-mm kernels have finally been fixed by this <a href="http://www.uwsg.indiana.edu/hypermail/linux/kernel/0505.0/0005.html">patch</a> from Oleg Nesterov.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">26</post-id>	</item>
		<item>
		<title>Lockups with 2.6.12-rc-mm on PPC64</title>
		<link>/articles/lockups-with-2612-rc-mm-on-ppc64/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Tue, 19 Apr 2005 01:30:42 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/04/19/lockups-with-2612-rc-mm-on-ppc64/</guid>

					<description><![CDATA[After many cycles of compiling and testing ppc64 kernels, I finally found out what causes 2.6.12-rc-mm kernels to lock up my PowerMac G5 regularly: It&#8217;s the recent changes in kernel/timer.c. When I exclude the timer-* patches from the mm series everything works fine again. I have not found a bug in these patches yet but<br />[&#8594; <a href="/articles/lockups-with-2612-rc-mm-on-ppc64/" class="more-link">Read the rest of this entry</a>]]]></description>
										<content:encoded><![CDATA[<p>After many cycles of compiling and testing ppc64 kernels, I finally found out what causes 2.6.12-rc-mm kernels to lock up my PowerMac G5 regularly: It&#8217;s the recent changes in <code>kernel/timer.c</code>.<br />
When I exclude the <code>timer-*</code> patches from the mm series everything works fine again.</p>
<p>I have not found a bug in these patches yet but I am pretty sure that it is no GCC bug.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">24</post-id>	</item>
		<item>
		<title>PowerMac G5 ALSA Driver</title>
		<link>/articles/powermac-g5-alsa-driver/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Mon, 11 Apr 2005 18:03:19 +0000</pubDate>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/04/11/powermac-g5-alsa-driver/</guid>

					<description><![CDATA[Thanks to this patch from Benjamin Herrenschmidt, there finally is sound support for the PowerMac G5! It even works with ppc64 kernels. Now if 2.6.12-rc kernels were just a tiny bit more stable on my G5&#8230;]]></description>
										<content:encoded><![CDATA[<p>Thanks to this <a href="http://ozlabs.org/pipermail/linuxppc64-dev/2005-April/003778.html">patch</a> from Benjamin Herrenschmidt, there finally is sound support for the PowerMac G5! It even works with ppc64 kernels.</p>
<p>Now if 2.6.12-rc kernels were just a tiny bit more stable on my G5&#8230;</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">23</post-id>	</item>
		<item>
		<title>PER_LINUX32 Fixes for Linux/ppc64</title>
		<link>/articles/per_linux32-fixes-for-linuxppc64/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Sun, 03 Apr 2005 22:19:13 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/04/04/per_linux32-fixes-for-linuxppc64/</guid>

					<description><![CDATA[I&#8217;ve tried to rebuild the latest Debian packages of Mozilla and Firefox with my jsarena pointer arithmetic fix on ppc32/ppc64 today. Rebuilding worked fine with older versions but this time it failed because the makefiles identified my G5 as an i386 box! The makefiles use uname -m to determine the CPU type, there&#8217;s no code<br />[&#8594; <a href="/articles/per_linux32-fixes-for-linuxppc64/" class="more-link">Read the rest of this entry</a>]]]></description>
										<content:encoded><![CDATA[<p>I&#8217;ve tried to rebuild the latest Debian packages of Mozilla and Firefox with my jsarena pointer arithmetic <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=279273">fix</a> on ppc32/ppc64 today. Rebuilding worked fine with older versions but this time it failed because the makefiles identified my G5 as an i386 box! The makefiles use <code>uname -m</code> to determine the CPU type, there&#8217;s no code to handle &#8216;ppc64&#8217; and the default is &#8216;x86&#8217;.</p>
<p>As my old work-around (providing a <code>uname</code> command that returns &#8216;ppc&#8217;) didn&#8217;t work anymore, this forced me to look at the root cause of the problem.</p>
<p>I&#8217;ve finally found two issues with the <code>PER_LINUX32</code> personality:</p>
<ul>
<li><code>uname(2)</code> didn&#8217;t respect <code>PER_LINUX32</code></li>
<li>Child processes didn&#8217;t inherit <code>PER_LINUX32</code></li>
</ul>
<p>This <a href="/static/kernel/per_linux32-2.6.12-rc1-mm4.patch">patch</a> for 2.6.12-rc1-mm4 fixes both issues:</p>
<pre>$ uname -m
ppc64
$ linux32 uname -m
ppc
$ linux32 sh -c &quot;uname -m&quot;
ppc</pre>
<p>Without the patch all three commands return &#8216;ppc64&#8217;.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">22</post-id>	</item>
		<item>
		<title>32-bit compat patch for inotify-0.21</title>
		<link>/articles/32-bit-compat-patch-for-inotify-021/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Thu, 17 Mar 2005 04:13:08 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/03/17/32-bit-compat-patch-for-inotify-021/</guid>

					<description><![CDATA[The inotify API has been changed, watches are now added via the file&#8217;s fd. That makes the 32-bit compat patch pretty trivial: inotify-0.21-compat.patch March 18th, 2005: The patch has been integrated into inotify 0.21-2]]></description>
										<content:encoded><![CDATA[<p>The <a href="http://www.kernel.org/pub/linux/kernel/people/rml/inotify/">inotify</a> API has been changed, watches are now added via the file&#8217;s fd. That makes the 32-bit compat patch pretty trivial:<br />
<a href="/static/kernel/inotify-0.21-compat.patch">inotify-0.21-compat.patch</a></p>
<p><em><strong>March 18th, 2005:</strong> The patch has been integrated into inotify 0.21-2</em></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">18</post-id>	</item>
		<item>
		<title>evdev compat patch now in -mm kernel</title>
		<link>/articles/evdev-compat-patch-now-in-mm-kernel/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Wed, 16 Mar 2005 19:34:39 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/03/16/evdev-compat-patch-now-in-mm-kernel/</guid>

					<description><![CDATA[My 32-bit compat patch for evdev has been integrated into Linux 2.6.11-mm3.]]></description>
										<content:encoded><![CDATA[<p>My <a href="/2005/02/28/32-bit-compat-evdev-driver/">32-bit compat patch</a> for evdev has been integrated into Linux 2.6.11-mm3.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17</post-id>	</item>
		<item>
		<title>32-bit compat ioctl for inotify</title>
		<link>/articles/32-bit-compat-ioctl-for-inotify/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Fri, 11 Mar 2005 01:30:08 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/03/11/32-bit-compat-ioctl-for-inotify/</guid>

					<description><![CDATA[I&#8217;ve just installed the file alteration monitor Gamin. Its inotify support didn&#8217;t work because inotify didn&#8217;t provide the required compat ioctl(2) for my mixed 32/64-bit system. Here&#8217;s a patch that adds the missing ioctl(2) to 2.6.11-mm2: inotify-compat-2.6.11-mm2.patch March 17th, 2005: Updated patch available here]]></description>
										<content:encoded><![CDATA[<p>I&#8217;ve just installed the file alteration monitor <a href="http://www.gnome.org/~veillard/gamin/">Gamin</a>. Its <a href="http://www.kernel.org/pub/linux/kernel/people/rml/inotify/">inotify</a> support didn&#8217;t work because inotify didn&#8217;t provide the required compat <code>ioctl(2)</code> for my mixed 32/64-bit system.<br />
Here&#8217;s a patch that adds the missing <code>ioctl(2)</code> to 2.6.11-mm2: <br /><a href="/static/kernel/inotify-compat-2.6.11-mm2.patch">inotify-compat-2.6.11-mm2.patch</a></p>
<p><em><strong>March 17th, 2005:</strong> Updated patch available <a href="/2005/03/17/32-bit-compat-patch-for-inotify-021/">here</a></em></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10</post-id>	</item>
		<item>
		<title>32-bit compat evdev driver</title>
		<link>/articles/32-bit-compat-evdev-driver/</link>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Mon, 28 Feb 2005 20:39:51 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Kernel]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/03/08/32-bit-compat-evdev-driver/</guid>

					<description><![CDATA[I&#8217;m running a ppc64 kernel with ppc32. This combination has a few shortcomings. One was that the kernel&#8217;s evdev driver had no 32-bit compatibility. I couldn&#8217;t use XFree86&#8217;s evdev support because of this, and hal had some problems too. I finally was annoyed enough to hack the evdev driver. Here&#8217;s the ugly patch: evdev-compat-2.6.11-rc3-mm2.patch March<br />[&#8594; <a href="/articles/32-bit-compat-evdev-driver/" class="more-link">Read the rest of this entry</a>]]]></description>
										<content:encoded><![CDATA[<p>I&#8217;m running a ppc64 kernel with ppc32. This combination has a few shortcomings.  One was that the kernel&#8217;s evdev driver had no 32-bit compatibility. I couldn&#8217;t use XFree86&#8217;s evdev support because of this, and <a href="http://www.freedesktop.org/Software/hal">hal</a> had some problems too. I finally was annoyed enough to hack the evdev driver.  Here&#8217;s the ugly patch:<br />
<a href="/static/kernel/evdev-compat-2.6.11-rc3-mm2.patch">evdev-compat-2.6.11-rc3-mm2.patch</a></p>
<p><em><strong>March 16th, 2005:</strong> The patch has been integrated into 2.6.11-mm3</em></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">5</post-id>	</item>
	</channel>
</rss>
