<?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>blog.world3.net</title>
	<atom:link href="http://blog.world3.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.world3.net</link>
	<description>たとえ溺れても梦はゆめでしかない</description>
	<lastBuildDate>Sat, 12 May 2012 09:44:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>RDP connection shortcut</title>
		<link>http://blog.world3.net/2012/05/rdp-connection-shortcut/</link>
		<comments>http://blog.world3.net/2012/05/rdp-connection-shortcut/#comments</comments>
		<pubDate>Sat, 12 May 2012 09:44:14 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=478</guid>
		<description><![CDATA[Create a shortcut with the target &#8220;%windir%\system32\mstsc.exe &#60;connection.rdp&#62;&#8221;. You can then pin it to the start menu or task bar for one click access.]]></description>
			<content:encoded><![CDATA[<p>Create a shortcut with the target &#8220;%windir%\system32\mstsc.exe &lt;connection.rdp&gt;&#8221;. You can then pin it to the start menu or task bar for one click access.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/05/rdp-connection-shortcut/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Japanese keyboard fix</title>
		<link>http://blog.world3.net/2012/05/japanese-keyboard-fix/</link>
		<comments>http://blog.world3.net/2012/05/japanese-keyboard-fix/#comments</comments>
		<pubDate>Thu, 10 May 2012 22:35:36 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=475</guid>
		<description><![CDATA[To fix the Japanese keyboard mapping on various laptops change the driver for the keyboard as well as the keyboard layout selection.]]></description>
			<content:encoded><![CDATA[<p>To fix the Japanese keyboard mapping on various laptops change the driver for the keyboard as well as the keyboard layout selection.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/05/japanese-keyboard-fix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Working XMEGA temperature sensor code</title>
		<link>http://blog.world3.net/2012/04/working-xmega-temperature-sensor-code/</link>
		<comments>http://blog.world3.net/2012/04/working-xmega-temperature-sensor-code/#comments</comments>
		<pubDate>Tue, 17 Apr 2012 08:00:30 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[avr]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=472</guid>
		<description><![CDATA[int16_t ref, degrees_x10; float kelvin_per_adc_x10; ADCA.CTRLA = ADC_FLUSH_bm; // cancel any pending conversions, disable ADC // set up exactly how Atmel did when they measured the calibration value ADCA.CTRLB = ADC_RESOLUTION_12BIT_gc; // unsigned conversion, produces result in range 0-2048 ADCA.REFCTRL = ADC_REFSEL_INT1V_gc &#124; ADC_TEMPREF_bm; ADCA.PRESCALER = ADC_PRESCALER_DIV512_gc; ADCA.CH0.CTRL = ADC_CH_INPUTMODE_INTERNAL_gc &#124; ADC_CH_GAIN_1X_gc; ADCA.CH0.MUXCTRL = ADC_CH_MUXINT_TEMP_gc; [...]]]></description>
			<content:encoded><![CDATA[<pre>int16_t ref, degrees_x10;
 float kelvin_per_adc_x10;</pre>
<pre>ADCA.CTRLA = ADC_FLUSH_bm; // cancel any pending conversions, disable ADC</pre>
<pre>// set up exactly how Atmel did when they measured the calibration value
 ADCA.CTRLB = ADC_RESOLUTION_12BIT_gc; // unsigned conversion, produces result in range 0-2048
 ADCA.REFCTRL = ADC_REFSEL_INT1V_gc | ADC_TEMPREF_bm;
 ADCA.PRESCALER = ADC_PRESCALER_DIV512_gc;</pre>
<pre>ADCA.CH0.CTRL = ADC_CH_INPUTMODE_INTERNAL_gc | ADC_CH_GAIN_1X_gc;
 ADCA.CH0.MUXCTRL = ADC_CH_MUXINT_TEMP_gc;</pre>
<pre>ADCA.CTRLA |= ADC_ENABLE_bm;
 adc_wait_8mhz();</pre>
<pre>// get 358 K factory calibrated value
 ref = HW_read_signature_byte(PROD_SIGNATURES_START + TEMPSENSE0);
 ref += HW_read_signature_byte(PROD_SIGNATURES_START + TEMPSENSE1) &lt;&lt; 8;
 kelvin_per_adc_x10 = ((273 + 85)*10) / (float)ref; // reference is ADC reading at 85C, scaled by 10 to get units of 0.1C</pre>
<pre>degrees_x10 = ADC_sample(&amp;ADCA.CH0);
 ADCA.CTRLA = 0; // turn ADC off
 ADCA.REFCTRL = 0; // turn temperature sensor off</pre>
<pre>degrees_x10 *= kelvin_per_adc_x10;</pre>
<pre>degrees_x10 -= 2730;</pre>
<pre>return (degrees_x10);</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/04/working-xmega-temperature-sensor-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HP Microserver early impressions</title>
		<link>http://blog.world3.net/2012/04/hp-microserver-early-impressions/</link>
		<comments>http://blog.world3.net/2012/04/hp-microserver-early-impressions/#comments</comments>
		<pubDate>Mon, 09 Apr 2012 21:26:18 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[hardware]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=467</guid>
		<description><![CDATA[The HP Microserver has been well reviewed on many sites, including Silent PC Review. Unfortunately it doesn&#8217;t live up to the hype, as many other people have discovered (check the SPCR and AVForums forums). The fans are loud. HP claim 22dB, but my basic meter rated the Microserver at 48dB from 1m. I swapped the [...]]]></description>
			<content:encoded><![CDATA[<p>The HP Microserver has been well reviewed on many sites, including Silent PC Review. Unfortunately it doesn&#8217;t live up to the hype, as many other people have discovered (check the SPCR and AVForums forums).</p>
<p>The fans are loud. HP claim 22dB, but my basic meter rated the Microserver at 48dB from 1m. I swapped the 120mm fan for a quieter one which reduced it down to an acceptable level, but even so the PSU fan is far too loud to use as a media centre. Definitely the sort of thing you need to keep out of the living room and bedroom.</p>
<p>The PSU is also far less efficient than the review models. SPCR measured an idle power consumption of 25W with two hard drives. As shipping the Microserver comes with one 250GB HDD and idles at 52W. More than twice what the review samples used. This is a common trick &#8211; send review sites units with special high efficiency components but ship much cheaper parts to consumers. I confirmed that the PSU is at fault by trying a more efficient one which did manage to reach 27W at idle.</p>
<p>Other than these two serious issues the server is a very nice bit of kit. The CPU seems reasonably powerful, a bit quicker than my older Atom D510 despite that CPU having hyperthreading. Plenty of room for HDDs (you can actually have 6 if you use the 3.5&#8243; bay and the external SATA) and fairly easy to work on. Seems solidly built. The unusual torx screw heads are a bit annoying and the multi-SATA cable is difficult to remove (necessary to slide the mobo out for RAM upgrades and the like). The GPU is powerful enough to do transcoding on the fly for DLNA. Some people have commented that the lack of a HDMI port makes it less useful as a media centre, but it is far too loud for that anyway.</p>
<p>The on-board network chip is a Broadcom NetXtream. It isn&#8217;t particularly good, strange for a machine basically built to serve files over a network. I can pull 60MB/sec over it, although CPU load is a bit high. There is no jumbo frame support, which isn&#8217;t as bad as it sounds because interrupt moderation makes it less important these days, but still&#8230; This is a budget chip. PCI-Express NICs are pretty cheap, but will of course add to the power consumption.</p>
<p>The BIOS is really basic. There is no fan speed control. Very little in the way of configurability for SATA operation, boot order and the like. The minimum shared memory for graphics is 32MB. The BIOS won&#8217;t boot with slow fans. SPCR says the cut-off is around 500 RPM, but I couldn&#8217;t go any lower than about 900 RPM.</p>
<p>Overall I&#8217;d say it&#8217;s a good product, if you are willing to accept the noise and either pay the higher electricity bills or shell out for a PicoPSU. As ever HP managed to take a good idea and almost ruin it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/04/hp-microserver-early-impressions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Possible fix for XBMC buffering issue</title>
		<link>http://blog.world3.net/2012/04/possible-fix-for-xbmc-buffering-issue/</link>
		<comments>http://blog.world3.net/2012/04/possible-fix-for-xbmc-buffering-issue/#comments</comments>
		<pubDate>Mon, 02 Apr 2012 21:00:46 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=465</guid>
		<description><![CDATA[Since day one I have had an issue with XMBC on Windows where it would occasionally need to buffer videos. I thought it was network related but there is no bandwidth problem and changing network card didn&#8217;t help. There was no problem with CPU usage either. Most bizarrely the problem would go away if I [...]]]></description>
			<content:encoded><![CDATA[<p>Since day one I have had an issue with XMBC on Windows where it would occasionally need to buffer videos. I thought it was network related but there is no bandwidth problem and changing network card didn&#8217;t help. There was no problem with CPU usage either. Most bizarrely the problem would go away if I altered the audio settings, e.g. by setting or clearing the &#8220;output stereo to all speakers&#8221; option. It didn&#8217;t matter what the actual settings were, they just had to be changed once per video. Even after starting and stopping the video it would stay fixed.</p>
<p>Today I switched from using the Radeon 3200 based on-board graphics to a discrete Radeon 5300 card and the problem seems to have gone. It must be something about the HDMI sound output or otherwise related to the card. Very odd.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/04/possible-fix-for-xbmc-buffering-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>40p tax rate ≠ rich people paying more tax</title>
		<link>http://blog.world3.net/2012/03/40p-tax-rate-%e2%89%a0-rich-people-paying-more-tax/</link>
		<comments>http://blog.world3.net/2012/03/40p-tax-rate-%e2%89%a0-rich-people-paying-more-tax/#comments</comments>
		<pubDate>Sat, 24 Mar 2012 20:55:28 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[politics]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=463</guid>
		<description><![CDATA[The idea being scrapping the 50p tax rate is that somehow it will make rich people pay more tax. That doesn&#8217;t seem to make sense. When the rate goes down will people paying the higher rate ask their accountants to stop dodging tax and decide that it&#8217;s now okay to pay more? Ah! But we [...]]]></description>
			<content:encoded><![CDATA[<p>The idea being scrapping the 50p tax rate is that somehow it will make rich people pay more tax. That doesn&#8217;t seem to make sense. When the rate goes down will people paying the higher rate ask their accountants to stop dodging tax and decide that it&#8217;s now okay to pay more?</p>
<p>Ah! But we are closing all the loop holes too, they say. Okay, close them, and keep the rate at 50p as well. Just&#8230; fucking tax the bastards.</p>
<p>Sorry, that was uncalled for. They are not all bastards. I&#8217;m really upset with the betrayal.  You expect the Torys to be dicks, but the Lib Dems made me<em> vote</em> for them. To be fair I don&#8217;t think Charles Kennedy would have ever shacked up with Cameron, and I never voted for Clegg (admittedly due to tactical voting, but still my hands are relatively unsoiled).</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/03/40p-tax-rate-%e2%89%a0-rich-people-paying-more-tax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RFM12B reception</title>
		<link>http://blog.world3.net/2012/03/rfm12b-reception/</link>
		<comments>http://blog.world3.net/2012/03/rfm12b-reception/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 15:28:40 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[avr]]></category>
		<category><![CDATA[electronics]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=461</guid>
		<description><![CDATA[Been debugging some RFM12B code again today. Reception is not as simple a matter as it could be because the documentation doesn&#8217;t really explain how it is supposed to work. I will try to make up for that in this post. Turn on receiver Wait for IRQ to indicate data available While RSSI bit in [...]]]></description>
			<content:encoded><![CDATA[<p>Been debugging some RFM12B code again today. Reception is not as simple a matter as it could be because the documentation doesn&#8217;t really explain how it is supposed to work. I will try to make up for that in this post.</p>
<ol>
<li>Turn on receiver</li>
<li>Wait for IRQ to indicate data available</li>
<li>While RSSI bit in status word is set keep reading data as IRQ indicates it is coming in</li>
<li>Reset FIFO</li>
</ol>
<p>The example code in the datasheet looks for an end-of-packet marker in step 3, which is also a workable option but has the disadvantage that the packet marker can never appear anywhere else in the packet. If your packets contain arbitrary data it&#8217;s possible an end-of-packet sequence like 0xAA55AA55 might appear in them, making those particular ones impossible to transmit. Instead I look for RSSI dropping and then decode what I have in the buffer independently of exactly how many bytes were received.</p>
<p>Step 4 is also rather critical. Without it you will keep getting IRQs signalling new data in the FIFO. The RFM12B picks up the preamble bytes which start the FIFO filling but does not seem to have any mechanism for stopping it again. You have to send the reset commands given in the datasheet or it will just keep receiving crap, even once RSSI disappears and it should be obvious that no new valid data is going to arrive.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/03/rfm12b-reception/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CCITT CRC for AVR in C</title>
		<link>http://blog.world3.net/2012/03/ccitt-crc-for-avr-in-c/</link>
		<comments>http://blog.world3.net/2012/03/ccitt-crc-for-avr-in-c/#comments</comments>
		<pubDate>Tue, 06 Mar 2012 09:35:46 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[avr]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=459</guid>
		<description><![CDATA[AVG libc comes with some handy CCITT CRC code, but I had trouble matching it to standard C implementations. Antov on AVR Freaks delivered: unsigned char a,b,c,d;  a = (unsigned char)((crc &#38; 0x00FF) ^ data);  b = (unsigned char)((a &#60;&#60; 4) ^ a);  c = (unsigned char)((b &#60;&#60; 3) ^ (crc &#62;&#62; 8) ^ ((b [...]]]></description>
			<content:encoded><![CDATA[<p>AVG libc comes with some handy CCITT CRC code, but I had trouble matching it to standard C implementations. <a href="http://www.avrfreaks.net/index.php?name=PNphpBB2&amp;file=viewtopic&amp;p=126695#126695">Antov on AVR Freaks</a> delivered:</p>
<pre>unsigned char a,b,c,d; 
a = (unsigned char)((crc &amp; 0x00FF) ^ data); 
b = (unsigned char)((a &lt;&lt; 4) ^ a); 
c = (unsigned char)((b &lt;&lt; 3) ^ (crc &gt;&gt; 8) ^ ((b &amp; 0xFF) &gt;&gt; 4)); 
d = (unsigned char)(b ^ ((b &amp; 0xFF) &gt;&gt; 5)); 
crc = (unsigned int)(((unsigned int)d &lt;&lt; 8)|(c &amp; 0xFF));</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/03/ccitt-crc-for-avr-in-c/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AVR bootloader linking</title>
		<link>http://blog.world3.net/2012/02/avr-bootloader-linking/</link>
		<comments>http://blog.world3.net/2012/02/avr-bootloader-linking/#comments</comments>
		<pubDate>Mon, 20 Feb 2012 11:19:02 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[avr]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=455</guid>
		<description><![CDATA[To link an AVR bootloader add this to the linker command line: -Wl,--section-start=.text=$(BOOT_START),-e,boot,--defsym,zero_addr=0 -nostdlib From http://old.nabble.com/Relocate-Data-into-bootloader-Section-td28511592.html]]></description>
			<content:encoded><![CDATA[<p>To link an AVR bootloader add this to the linker command line:</p>
<pre>-Wl,--<strong>section</strong>-start=.text=$(BOOT_START),-e,boot,--defsym,zero_addr=0 -nostdlib</pre>
<p>From <a href="http://old.nabble.com/Relocate-Data-into-bootloader-Section-td28511592.html">http://old.nabble.com/Relocate-Data-into-bootloader-Section-td28511592.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/02/avr-bootloader-linking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>XMEGA USART unsets output direction on ports when disabling TX</title>
		<link>http://blog.world3.net/2012/02/xmega-usart-unsets-output-direction-on-ports-when-disabling-tx/</link>
		<comments>http://blog.world3.net/2012/02/xmega-usart-unsets-output-direction-on-ports-when-disabling-tx/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 15:23:46 +0000</pubDate>
		<dc:creator>mojo</dc:creator>
				<category><![CDATA[avr]]></category>

		<guid isPermaLink="false">http://blog.world3.net/?p=452</guid>
		<description><![CDATA[I noticed that if I set the TX pin of a port to output and then enable the USART it works. If I then disable the TXEN bit (necessary because with IR comms the TX line has to be held low during reception, otherwise the transceiver blinds itself) the TX port pin is reset to being an [...]]]></description>
			<content:encoded><![CDATA[<p>I noticed that if I set the TX pin of a port to output and then enable the USART it works. If I then disable the TXEN bit (necessary because with IR comms the TX line has to be held low during reception, otherwise the transceiver blinds itself) the TX port pin is reset to being an input. Unless you set it back to being an output the USART will be unable to send any more data when you re-enabled TXEN.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.world3.net/2012/02/xmega-usart-unsets-output-direction-on-ports-when-disabling-tx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

