<?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/"
	>

<channel>
	<title>Humboldt Solutions Ltd &#187; linux</title>
	<atom:link href="http://www.humboldt.co.uk/tag/linux/feed" rel="self" type="application/rss+xml" />
	<link>http://www.humboldt.co.uk</link>
	<description>Software Development and Consulting</description>
	<lastBuildDate>Sat, 06 Jun 2009 08:28:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>fsync() Across Platforms</title>
		<link>http://www.humboldt.co.uk/2009/03/fsync-across-platforms.html</link>
		<comments>http://www.humboldt.co.uk/2009/03/fsync-across-platforms.html#comments</comments>
		<pubDate>Mon, 16 Mar 2009 22:21:35 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[notes]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=164</guid>
		<description><![CDATA[When an application writes a file, the data does not become permanent immediately. The write operation first moves the data into the operating system cache in RAM, where it is vulnerable to system crashes and loss of power.  The second step is the transfer to the hard disk, which normally has write caching enabled. [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2009/03/fsync-across-platforms.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Working TFTP Server for Multi-Homed Linux Systems</title>
		<link>http://www.humboldt.co.uk/2008/11/a-working-tftp-server-for-multi-homed-linux-systems.html</link>
		<comments>http://www.humboldt.co.uk/2008/11/a-working-tftp-server-for-multi-homed-linux-systems.html#comments</comments>
		<pubDate>Thu, 13 Nov 2008 09:17:05 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[notes]]></category>
		<category><![CDATA[ip]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://www.humboldt.co.uk/?p=25</guid>
		<description><![CDATA[Linux machines with multiple network interfaces are unreliable as TFTP servers. This issue has been outstanding for a long time, without any resolution. The patch attached to the Debian bug fixes the problem for an old release of tftpd-hpa, but does not apply cleanly to recent releases.
Recent releases of dnsmasq contain a TFTP server which [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2008/11/a-working-tftp-server-for-multi-homed-linux-systems.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Running Linux on a PCI Add-in Card: Hardware</title>
		<link>http://www.humboldt.co.uk/2006/04/running-linux-on-a-pci-add-in-card-hardware.html</link>
		<comments>http://www.humboldt.co.uk/2006/04/running-linux-on-a-pci-add-in-card-hardware.html#comments</comments>
		<pubDate>Fri, 28 Apr 2006 10:54:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[notes]]></category>
		<category><![CDATA[embedded]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[pci]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/2006/04/running-linux-on-a-pci-add-in-card-hardware.html</guid>
		<description><![CDATA[Every so often I see someone attempting to run the Linux kernel on a PCI add-in card. I&#8217;ve done this myself, but there are a lot of complications. This article covers the hardware, and a second article will cover software. Don&#8217;t take this as chipset selection advice: before you commit to hardware double-check both the [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2006/04/running-linux-on-a-pci-add-in-card-hardware.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>In the Year 2038</title>
		<link>http://www.humboldt.co.uk/2006/02/in-the-year-2038.html</link>
		<comments>http://www.humboldt.co.uk/2006/02/in-the-year-2038.html#comments</comments>
		<pubDate>Wed, 15 Feb 2006 21:29:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[notes]]></category>
		<category><![CDATA[2038]]></category>
		<category><![CDATA[embedded]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/2006/02/in-the-year-2038.html</guid>
		<description><![CDATA[I have now seen my first ever year 2038  bug. An embedded Linux system that was installed two years ago became unable to acquire a network address by DHCP. The machine did not require an accurate clock, and nobody had initialised its battery-backed real-time clock. Once installed, it had started counting forward from 1st [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2006/02/in-the-year-2038.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Slow Reboots of NFS Server</title>
		<link>http://www.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html</link>
		<comments>http://www.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html#comments</comments>
		<pubDate>Wed, 01 Feb 2006 16:02:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[notes]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[nfs]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html</guid>
		<description><![CDATA[After several years of use, the server for my development machines developed a problem. If I rebooted the machine without an internet connection, it would pause for several minutes while starting the NFS service.
The Linux NFS server keeps track of status in several files. Whenever a client mounts a filesystem, the server records this in [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2006/02/slow-reboots-of-nfs-server.html/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>MPC107/Tsi107 I2C in Linux 2.6</title>
		<link>http://www.humboldt.co.uk/2004/08/mpc107tsi107-i2c-in-linux-26.html</link>
		<comments>http://www.humboldt.co.uk/2004/08/mpc107tsi107-i2c-in-linux-26.html#comments</comments>
		<pubDate>Tue, 24 Aug 2004 00:00:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[i2c]]></category>
		<category><![CDATA[driver]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[powerpc]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/1970/01/mpc107tsi107-i2c-in-linux-26.html</guid>
		<description><![CDATA[As of Linux 2.6.9.1, the driver is in the kernel as i2c-mpc.c. This version of the driver has been tested on Tsi107 (formerly MPC107), and on MPC8240, MPC8540, and MPC5200 PowerPCs. Thanks to all the testers.
]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2004/08/mpc107tsi107-i2c-in-linux-26.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MPC107/Tsi107 Cache Coherency</title>
		<link>http://www.humboldt.co.uk/2004/08/mpc107tsi107-cache-coherency.html</link>
		<comments>http://www.humboldt.co.uk/2004/08/mpc107tsi107-cache-coherency.html#comments</comments>
		<pubDate>Wed, 18 Aug 2004 00:00:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[notes]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[powerpc]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/1970/01/mpc107tsi107-cache-coherency.html</guid>
		<description><![CDATA[The Tsi106 (formerly MPC106) and Tsi107 (formerly MPC107) PowerPC host bridges both contain a data cache. This note describes why it may be necessary to mark memory as SMP coherent even in a single processor system using these bridges.

60x family PowerPCs, such as the MPC603e and MPC7447 have the option of marking memory as coherent [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2004/08/mpc107tsi107-cache-coherency.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MPC107 I2C Driver</title>
		<link>http://www.humboldt.co.uk/2003/03/mpc107-i2c-driver.html</link>
		<comments>http://www.humboldt.co.uk/2003/03/mpc107-i2c-driver.html#comments</comments>
		<pubDate>Sat, 29 Mar 2003 00:00:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[i2c]]></category>
		<category><![CDATA[driver]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[powerpc]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/1970/01/mpc107-i2c-driver.html</guid>
		<description><![CDATA[The driver is supplied ready to be inserted into the linuxppc-2.4-devel tree.
The driver has so far been tested on a small number of systems and with a small number of I2C parts. Thanks to Gleb Natapov, Matthew S. McClintock, and others for testing. Further test results are welcome.


i2c-adap-mpc10x-0.3.c Corrected transfer function to return number of [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2003/03/mpc107-i2c-driver.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Asiliant 69030 Driver for Linux 2.2</title>
		<link>http://www.humboldt.co.uk/2002/11/asiliant-69030-driver-for-linux-22.html</link>
		<comments>http://www.humboldt.co.uk/2002/11/asiliant-69030-driver-for-linux-22.html#comments</comments>
		<pubDate>Wed, 20 Nov 2002 00:00:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[asiliant]]></category>
		<category><![CDATA[69030]]></category>
		<category><![CDATA[driver]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/1970/01/asiliant-69030-driver-for-linux-22.html</guid>
		<description><![CDATA[These are experimental Linux 2.2 and 2.4 framebuffer drivers for the Asiliant 69030 graphics chip. This chip was previously available from Intel, and is descended from a Chips and Technologies part. The 2.2 driver is thus based on the Linux chipsfb.c driver, which supports the 65555 part in certain Apple Powerbooks. The 2.4 driver is [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2002/11/asiliant-69030-driver-for-linux-22.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Asiliant 69030 Driver for Linux 2.4</title>
		<link>http://www.humboldt.co.uk/2002/11/asiliant-69030-driver-for-linux-24.html</link>
		<comments>http://www.humboldt.co.uk/2002/11/asiliant-69030-driver-for-linux-24.html#comments</comments>
		<pubDate>Wed, 20 Nov 2002 00:00:00 +0000</pubDate>
		<dc:creator>Adrian Cox</dc:creator>
				<category><![CDATA[asiliant]]></category>
		<category><![CDATA[69030]]></category>
		<category><![CDATA[driver]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://testwww.humboldt.co.uk/1970/01/asiliant-69030-driver-for-linux-24.html</guid>
		<description><![CDATA[These are experimental Linux 2.2 and 2.4 framebuffer drivers for the Asiliant 69030 graphics chip. This chip was previously available from Intel, and is descended from a Chips and Technologies part. The 2.2 driver is thus based on the Linux chipsfb.c driver, which supports the 65555 part in certain Apple Powerbooks. The 2.4 driver is [...]]]></description>
		<wfw:commentRss>http://www.humboldt.co.uk/2002/11/asiliant-69030-driver-for-linux-24.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
