<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>StrangeWorlds</title>
	<link>http://strangeworlds.co.uk/blog</link>
	<description>The website experience</description>
	<lastBuildDate>Sun, 02 May 2010 18:03:47 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Slackware -current &amp; Radeon KMS</title>
		<description><![CDATA[It works.
Suspend to RAM appears to be broken (but I haven&#8217;t tested that in ages, so might have been broken anyway), but other than that, I&#8217;m now running with a custom 2.6.33.3 kernel with KMS enabled on my old Aspire 5021 (Radeon Mobility X700), and it appears to be ok (it can be a bit [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2010/05/02/slackware-current-radeon-kms/</link>
			</item>
	<item>
		<title>KDE &amp; Exchange support</title>
		<description><![CDATA[I&#8217;ve been spending the last few weeks, on and off, trying to figure out the level of Microsoft Exchange support in KDE at the present moment and near future. From lots of digging around various sites, and poking at the source code, it seems that:
1) libmapi (from OpenChange) provides a library that can talk to [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2010/01/19/kde-exchange-support/</link>
			</item>
	<item>
		<title>Using a non-US keyboard in X with Slackware -current (13.0) without xorg.conf</title>
		<description><![CDATA[xorg.conf is dead &#8211; long live xorg.conf
For a UK layout keyboard, stick the following in /etc/hal/fdi/policy/10-keymap.fdi (for other layouts, change gb and/ or add as appropriate).
This is just enough to merge with the existing file &#038; blat the keyboard layout (without having to resort to re-implementing the default Slackware FDI).

&#60;?xml version="1.0" encoding="ISO-8859-1"?&#62; &#60;!-- -*- SGML [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2009/06/10/using-a-non-us-keyboard-in-x-with-slackware-current-130-without-xorgconf/</link>
			</item>
	<item>
		<title>tc1100 &amp; rfkill</title>
		<description><![CDATA[tc1100 &#8211; The other WMI driver I maintain (the one that I&#8217;ve never even had the hardware for, let alone set eyes on, which always makes it &#8216;interesting&#8217; to work on).
I&#8217;ve posted patches to add rfkill support to this driver to the linux-acpi mailing list. If you:
1) Have the hardware
2) Can compile your own kernel
Then [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2008/10/10/tc1100-rfkill/</link>
			</item>
	<item>
		<title>rfkill update</title>
		<description><![CDATA[It&#8217;s been a while, so:
1) I&#8217;ve posted the final version of the patches to add rfkill support to acer-wmi on the 15th September to the ACPI mailing list.
_Hopefully_ these will go in for 2.6.28.
(This is only for wireless and bluetooth &#8211; still waiting for someone to use Linux on an Acer laptop that has built [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2008/09/29/rfkill-update/</link>
			</item>
	<item>
		<title>acer-wmi &amp; rfkill</title>
		<description><![CDATA[I&#8217;ve been experimenting now for the last few months with adding rfkill support to acer-wmi in my (rather limited these days) free time (the short, short version of &#8216;why&#8217; is that this will allow the wireless &#038; bluetooth buttons to just work out of the box on those laptops which have them properly mapped by [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2008/04/13/acer-wmi-rfkill/</link>
			</item>
	<item>
		<title>acer_acpi &#8211; Latest news</title>
		<description><![CDATA[I&#8217;ve been rather quiet lately, so time for the latest news:
1) The input part of acer_acpi (the keyboard quirks) has been accepted by Dmitry Torokhov (the input subsystem maintainer) into his tree. This will be going into 2.6.25 &#8211; this means that if you have one of the laptops that requires the old acerhk keyboard [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2008/01/29/acer_acpi-latest-news/</link>
			</item>
	<item>
		<title>AMW0 and hardware detection</title>
		<description><![CDATA[After re-reading an old readme &#038; history file bundled with a different release of Launch manager (the one available for the Aspire 1690 &#8211; same version as the 5020 version, but this EXL806WW.BLD.txt file is missing from the 5020 release), I finally figured out that:
1) It is actually possible to auto detect hardware on older [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2008/01/07/amw0-and-hardware-detection/</link>
			</item>
	<item>
		<title>My Christmas Presents</title>
		<description><![CDATA[
I wonder if people are trying to tell me something&#8230;?
]]></description>
		<link>http://strangeworlds.co.uk/blog/2007/12/26/my-christmas-presents/</link>
			</item>
	<item>
		<title>WMI &amp; acer-wmi news</title>
		<description><![CDATA[WMI: Latest version (v7) was published on the ACPI mailing lists (I finally figured out my problems). This work has been ported to acer_acpi already (and not a moment too soon, since the Aspire 7520 has multiple PNP0C14 devices).
acer-wmi: Initial RFC (request for comment aka first try, please review) has been posted to the ACPI [...]]]></description>
		<link>http://strangeworlds.co.uk/blog/2007/12/04/wmi-acer-wmi-news/</link>
			</item>
</channel>
</rss>
