<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Aki assembling a small mobile pool!</title>
	<atom:link href="http://oduinn.com/2008/11/26/aki-making-a-small-mobile-pool/feed/" rel="self" type="application/rss+xml" />
	<link>http://oduinn.com/blog/2008/11/26/aki-making-a-small-mobile-pool/</link>
	<description></description>
	<lastBuildDate>Fri, 27 Jan 2012 15:12:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Axel Hecht</title>
		<link>http://oduinn.com/blog/2008/11/26/aki-making-a-small-mobile-pool/#comment-12928</link>
		<dc:creator>Axel Hecht</dc:creator>
		<pubDate>Thu, 27 Nov 2008 12:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2008/11/26/aki-making-a-small-mobile-pool/#comment-12928</guid>
		<description>Both Lego and Fischertechnik offer pneumatics and computer interfaces, and some sensors. Should be possible to create something that pushes the powerbutton, waits for power down, pushes the power button again, waits for power up.

And at least for a German kid growing up with both, I&#039;d just love to see that in action :-)</description>
		<content:encoded><![CDATA[<p>Both Lego and Fischertechnik offer pneumatics and computer interfaces, and some sensors. Should be possible to create something that pushes the powerbutton, waits for power down, pushes the power button again, waits for power up.</p>
<p>And at least for a German kid growing up with both, I&#8217;d just love to see that in action <img src='http://oduinn.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://oduinn.com/blog/2008/11/26/aki-making-a-small-mobile-pool/#comment-12926</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 27 Nov 2008 12:03:11 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2008/11/26/aki-making-a-small-mobile-pool/#comment-12926</guid>
		<description>&quot;if the device hangs during a test, how do you powercycle it? (Most people first suggest removing battery and running on remote switchable a/c; however, these devices refuse to boot unless a battery is present, and it looks like they need a physical button pushed on after a power reset, so weâ€™re still looking for a solution - all suggestions welcome!)&quot;

You can powercycle the system via USB.  In theory that should always work.

&quot;How do these devices communicate to other machines; how do we get builds onto, and test data off from, these devices? The buildbot master needs to tell slaves when and what to do. The slaves need to post results to buildbot master as well as ftp.m.o and graphserver. Something (nagios?) needs to monitor to see if devices are ok. If we use wifi, does that cause noisy deviations in our test results? If we use ethernet, what s/w drivers and cable converters do we need?&quot;

I&#039;d suggest using USB networking.

&quot;What toolchain do we need to install on these devices? Both of these devices were â€œpollutedâ€ when we got them, meaning no-one was exactly sure whats on them, and weâ€™re fairly sure theyâ€™re different from each other. Weâ€™ve got some more machines on order, so will have to figure out clean-setup-instructions as part of this setup.&quot;

You should flash a clean copy of the latest Maemo onto the devices.  If you get enough devices that you can try more unusual configurations, consider also testing Mamona and Debian.

    * Is there enough memory in the device to run o.s. + buildbot + talos + talos-tools + fennec? Can far can we increase memory? Do we have to rewrite buildbot/talos to fit into low memory situations?

You probably don&#039;t have enough, no.</description>
		<content:encoded><![CDATA[<p>&#8220;if the device hangs during a test, how do you powercycle it? (Most people first suggest removing battery and running on remote switchable a/c; however, these devices refuse to boot unless a battery is present, and it looks like they need a physical button pushed on after a power reset, so weâ€™re still looking for a solution &#8211; all suggestions welcome!)&#8221;</p>
<p>You can powercycle the system via USB.  In theory that should always work.</p>
<p>&#8220;How do these devices communicate to other machines; how do we get builds onto, and test data off from, these devices? The buildbot master needs to tell slaves when and what to do. The slaves need to post results to buildbot master as well as <a href="http://ftp.m.o" rel="nofollow">http://ftp.m.o</a> and graphserver. Something (nagios?) needs to monitor to see if devices are ok. If we use wifi, does that cause noisy deviations in our test results? If we use ethernet, what s/w drivers and cable converters do we need?&#8221;</p>
<p>I&#8217;d suggest using USB networking.</p>
<p>&#8220;What toolchain do we need to install on these devices? Both of these devices were â€œpollutedâ€ when we got them, meaning no-one was exactly sure whats on them, and weâ€™re fairly sure theyâ€™re different from each other. Weâ€™ve got some more machines on order, so will have to figure out clean-setup-instructions as part of this setup.&#8221;</p>
<p>You should flash a clean copy of the latest Maemo onto the devices.  If you get enough devices that you can try more unusual configurations, consider also testing Mamona and Debian.</p>
<p>    * Is there enough memory in the device to run o.s. + buildbot + talos + talos-tools + fennec? Can far can we increase memory? Do we have to rewrite buildbot/talos to fit into low memory situations?</p>
<p>You probably don&#8217;t have enough, no.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

