Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 5e33e0e4a5eb18be5b8b0ccc88876c0e84738bff..745603a660fe5f0abba3b1f42583049c31adb3d1 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,22 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
+       <item>
+               <title>Perl library to control the Spykee robot moved to github</title>
+               <link>http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html</guid>
+                <pubDate>Sat, 19 Oct 2013 10:20:00 +0200</pubDate>
+               <description>&lt;p&gt;Back in 2010, I created a Perl library to talk to
+&lt;a href=&quot;http://en.wikipedia.org/wiki/Spykee&quot;&gt;the Spykee robot&lt;/a&gt;
+(with two belts, wifi, USB and Linux) and made it available from my
+web page.  Today I concluded that it should move to a site that is
+easier to use to cooperate with others, and moved it to github.  If
+you got a Spykee robot, you might want to check out
+&lt;a href=&quot;https://github.com/petterreinholdtsen/libspykee-perl&quot;&gt;the
+libspykee-perl github repository&lt;/a&gt;.&lt;/p&gt;
+</description>
+       </item>
+       
        <item>
                <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
                <link>http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</link>
@@ -948,34 +964,5 @@ stick ISO image.&lt;/li&gt;
 </description>
        </item>
        
-       <item>
-               <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
-               <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
-                <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
-               <description>&lt;p&gt;Earlier, I reported about
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html&quot;&gt;my
-problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;.  Friday I was
-told by IBM that the original disk should be thrown away.  And as
-there no longer was a problem if I bricked the firmware, I decided
-today to try to install Intel firmware to replace the Lenovo firmware
-currently on the disk.&lt;/p&gt;
-
-&lt;p&gt;I searched the Intel site for firmware, and found
-&lt;a href=&quot;https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&amp;ProdId=3472&amp;DwnldID=18363&amp;ProductFamily=Solid-State+Drives+and+Caching&amp;ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive&amp;ProductProduct=Intel%c2%ae+SSD+520+Series+(180GB%2c+2.5in+SATA+6Gb%2fs%2c+25nm%2c+MLC)&amp;lang=eng&quot;&gt;issdfut_2.0.4.iso&lt;/a&gt;
-(aka Intel SATA Solid-State Drive Firmware Update Tool) which
-according to the site should contain the latest firmware for SSD
-disks.  I inserted the broken disk in one of my spare laptops and
-booted the ISO from a USB stick.  The disk was recognized, but the
-program claimed the newest firmware already were installed and refused
-to insert any Intel firmware.  So no change, and the disk is still
-unable to handle write load. :( I guess the only way to get them
-working would be if Lenovo releases new firmware.  No idea how likely
-that is.  Anyway, just blogging about this test for completeness.  I
-got a working Samsung disk, and see no point in spending more time on
-the broken disks.&lt;/p&gt;
-</description>
-       </item>
-       
         </channel>
 </rss>