<?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>Andreas Schneider &#187; Hardware</title>
	<atom:link href="http://blog.cynapses.org/category/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cynapses.org</link>
	<description>a cosmological pedestrian</description>
	<lastBuildDate>Tue, 23 Feb 2010 10:17:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Geocaching, Garmin and Linux</title>
		<link>http://blog.cynapses.org/2009/01/17/geocaching-garmin-and-linux/</link>
		<comments>http://blog.cynapses.org/2009/01/17/geocaching-garmin-and-linux/#comments</comments>
		<pubDate>Sat, 17 Jan 2009 12:04:53 +0000</pubDate>
		<dc:creator>GlaDiaC</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Geocachiing]]></category>
		<category><![CDATA[GPS]]></category>

		<guid isPermaLink="false">http://blog.cynapses.org/?p=48</guid>
		<description><![CDATA[I'm a Geocacher and I've bought a new toy, the Garmin Vista HCx. This device has a special function for Geocaching. You have to upload these files directly to the device. It isn't possible to store them on the microSD. On the geocaching.com you have an option to send the coordinates directly to the GPS. [...]]]></description>
			<content:encoded><![CDATA[<p>I'm a <a href="http://en.wikipedia.org/wiki/Geocaching">Geocacher</a> and I've bought a new toy, the <a href="https://buy.garmin.com/shop/shop.do?cID=145&#038;pID=8703">Garmin Vista HCx</a>. This device has a special function for Geocaching. You have to upload these files directly to the device. It isn't possible to store them on the microSD.<br />
On the geocaching.com you have an option to send the coordinates directly to the GPS. It downloads a web browser plugin from Garmin. To send the files (.loc or .gps) to the device on Linux there is a nice tool called <a href="http://www.gpsbabel.org/">gpsbabel</a>. You can use it to send your files to the GPS. However the device supports only traditional caches <img src='http://blog.cynapses.org/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>So a simple script named "sendCache" is:</p>
<p><code>#!/bin/bash<br />
# sendCache<br />
gpsbabel -i gpx -f $1 -o garmin -F usb:</code></p>
<p>You have to remove the kernel module which is loaded automatically:</p>
<p><code>rmmod garmin_gps</code></p>
<p>Or blacklist it in /etc/modprobe.d/blacklist. Simply add 'blacklist garmin_gps'.</p>
<p>To get the permissions to work with gpsbabel as a user, you have to install a hal fdi file. Copy <a href="http://www.cynapses.org/tmp/80-gps.fdi">80-gps.fdi</a> to '/usr/share/hal/fdi/information/20thirdparty'. This will set acl rules for write access to the user if you attach it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cynapses.org/2009/01/17/geocaching-garmin-and-linux/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Hackweek3: Logitech hacking</title>
		<link>http://blog.cynapses.org/2008/08/26/hackweek3-logitech-hacking/</link>
		<comments>http://blog.cynapses.org/2008/08/26/hackweek3-logitech-hacking/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 14:59:18 +0000</pubDate>
		<dc:creator>GlaDiaC</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[SUSE]]></category>

		<guid isPermaLink="false">http://blog.cynapses.org/?p=35</guid>
		<description><![CDATA[I planning to rewrite lomoco since a long time now. The problem is that Logitech has introduced a new protocol to talk to the devices. For the main features of these new mice we have already proof of concept code but some features aren't suppport. I still don't know how they identify a cordless mouse [...]]]></description>
			<content:encoded><![CDATA[<p>I planning to rewrite <a href="http://www.lomoco.org/">lomoco</a> since a long time now. The problem is that Logitech has introduced a new protocol to talk to the devices. For the main features of these new mice we have already proof of concept code but some features aren't suppport.</p>
<p>I still don't know how they identify a cordless mouse connected to a receiver. The MX Revolution and the G7 share the same receiver. Yesterday I've discovered how to read the battery status from the MX and VX Revolution. I can display the battery status in percent and if the mouse is charging or is fully charged.</p>
<p>I've put together a proof-of-concept code <a href="http://www.lomoco.org/vx_hack.c">here</a>. Now it is time to think about a library, liblomoco. If someone is interested in hacking, feel free to contact me <img src='http://blog.cynapses.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>If you have a VX Nano or G7 please send me the output of the <a href="http://www.lomoco.org/vx_hack.c">vx_hack</a>. If you own a G7 please send me the output of the 'lsusb' command.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cynapses.org/2008/08/26/hackweek3-logitech-hacking/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>lomoco &#8211; next generation</title>
		<link>http://blog.cynapses.org/2007/04/24/lomoco-next-generation/</link>
		<comments>http://blog.cynapses.org/2007/04/24/lomoco-next-generation/#comments</comments>
		<pubDate>Tue, 24 Apr 2007 16:08:27 +0000</pubDate>
		<dc:creator>GlaDiaC</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://blog.cynapses.org/2007/04/24/lomoco-next-generation/</guid>
		<description><![CDATA[I've finished my diploma thesis (more about this later) and started to work on lomoco again. lomoco can configure vendor-specific options on Logitech USB mice (or dual-personality mice plugged into the USB port). Since there are some places where you can find code to control Logitech mice, I decided to write a shared library. We [...]]]></description>
			<content:encoded><![CDATA[<p>I've finished my diploma thesis (more about this later) and started to work on lomoco again. lomoco can configure vendor-specific options on Logitech USB mice (or dual-personality mice plugged into the USB port).<br />
Since there are some places where you can find code to control Logitech mice, I decided to write a shared library. We will provide a command line client to configure your mouse. The shared library makes it possible to use it for example in KDE's kcontrol which has his own code for Logitech mice at the moment.</p>
<p>Some days ago Peter Feuerer (<a href="http://www.piie.net/">piie</a>) was able to sniff the commands which have to be send to the G5 to change the resolution. With some already existing hiddev code, he was able to set the different resolution modes. The G5 has only 4 resolutions: 400, 800, 1600, 2000. The rest of the resolution you can select with the windows server is just interpolated! You can find the hack <a href="http://piie.net/temp/g5_hiddev.c">here</a>. There is existing code for the MX610 and MX Revolution too.</p>
<p>You can find the lomoco homepage <a href="http://lomoco.linux-gamers.net/">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cynapses.org/2007/04/24/lomoco-next-generation/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Bricked Linksys WRT54G repair instructions</title>
		<link>http://blog.cynapses.org/2007/01/17/bricked-linksys-wrt54g-repair-instructions/</link>
		<comments>http://blog.cynapses.org/2007/01/17/bricked-linksys-wrt54g-repair-instructions/#comments</comments>
		<pubDate>Wed, 17 Jan 2007 11:12:17 +0000</pubDate>
		<dc:creator>GlaDiaC</dc:creator>
				<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://blog.cynapses.org/2007/01/17/bricked-linksys-wrt54g-repair-instructions/</guid>
		<description><![CDATA[What you need: 1 bricked Linksys WRT54G router with boot_wait=off 1 corkscrew optional: 1 bottle of wine If you have to take courage first, the bottle of wine could help! What to do: Unscrew the antennas and open the router and look for the Intel flash chip. The chip has 48 pins. You can find [...]]]></description>
			<content:encoded><![CDATA[<p><strong>What you need:</strong></p>
<p>1 bricked Linksys WRT54G router with boot_wait=off<br />
1 corkscrew</p>
<p>optional:<br />
1 bottle of wine</p>
<p>If you have to take courage first, the bottle of wine could help!</p>
<p><strong>What to do:</strong></p>
<p>Unscrew the antennas and open the router and look for the Intel flash chip. The chip has 48 pins. You can find the numbers on the edges of the chip 1 .. 24 .. 25 .. 48. Time for a big slug of wine! Now use the corkscrew to shorten pin 16 and 17.</p>
<blockquote><p>I have the Linksys WRT54G v2.2, on some older routers you have to shorten pin 15 &#038; 16.</p></blockquote>
<p>Now plug in the power cable and your Linksys should be ping-able now. You can send the firmware using tftp:</p>
<p><font face="courier">tftp 192.168.1.1<br />
binary<br />
rexmt 1<br />
timeout 60<br />
trace<br />
tftp> put <em>firmwarefile</em>.bin</font></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cynapses.org/2007/01/17/bricked-linksys-wrt54g-repair-instructions/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
