<div dir="ltr">You can unsubscribe yourself at the bottom of this page<div><br></div><div><a href="http://lists.laptop.org/listinfo/devel">http://lists.laptop.org/listinfo/devel</a><br></div><div><br></div><div>Gonzalo</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Oct 7, 2013 at 1:08 PM, Anderson, Nicole A <span dir="ltr"><<a href="mailto:NAnderson@winona.edu" target="_blank">NAnderson@winona.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Unsubscribe me from this list please.<br>
<br>
> On Oct 7, 2013, at 11:01 AM, "<a href="mailto:devel-request@lists.laptop.org">devel-request@lists.laptop.org</a>" <<a href="mailto:devel-request@lists.laptop.org">devel-request@lists.laptop.org</a>> wrote:<br>
><br>
> Send Devel mailing list submissions to<br>
> <a href="mailto:devel@lists.laptop.org">devel@lists.laptop.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:devel-request@lists.laptop.org">devel-request@lists.laptop.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:devel-owner@lists.laptop.org">devel-owner@lists.laptop.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of Devel digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Android on the XO-4 (Sameer Verma)<br>
> 2. Re: Android on the XO-4 (Walter Bender)<br>
> 3. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron)<br>
> 4. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4<br>
> (Yioryos Asprobounitis)<br>
> 5. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Sun, 6 Oct 2013 11:03:05 -0700<br>
> From: Sameer Verma <<a href="mailto:sverma@sfsu.edu">sverma@sfsu.edu</a>><br>
> To: "Devel's in the Details" <<a href="mailto:devel@lists.laptop.org">devel@lists.laptop.org</a>>, John Gilmore<br>
> <<a href="mailto:gnu@toad.com">gnu@toad.com</a>><br>
> Subject: Android on the XO-4<br>
> Message-ID:<br>
> <<a href="mailto:CAFoGK8EjcHHG5UFBLpzCBQO838JaguXRiuEaP9%2BFv98EaVAgUA@mail.gmail.com">CAFoGK8EjcHHG5UFBLpzCBQO838JaguXRiuEaP9+Fv98EaVAgUA@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1<br>
><br>
> I was at the Internet Archive for some work on Pathagar<br>
> (<a href="https://github.com/PathagarBooks/pathagar" target="_blank">https://github.com/PathagarBooks/pathagar</a>). Also there that afternoon<br>
> was John Gilmore (cc'd). We got to talking about the XO-4, Android,<br>
> HTML5, etc. A bit of doodling on Physics, and John put together a two<br>
> cylinder engine, complete with a rocker arm :-) He also suggested the<br>
> possibility of CyanogenMod on the XO-4 as a starting point.<br>
><br>
> If there is any interest in this, please submit a proposal for the<br>
> upcoming OLPC SF summit<br>
> <a href="http://www.olpcsf.org/CommunitySummit2013/proposal" target="_blank">http://www.olpcsf.org/CommunitySummit2013/proposal</a><br>
><br>
> John,<br>
><br>
> If you are in town Oct 18-20, we'd love to have you there.<br>
> <a href="http://olpcsf.org/summit" target="_blank">http://olpcsf.org/summit</a><br>
><br>
> cheers,<br>
> Sameer<br>
> --<br>
> Sameer Verma, Ph.D.<br>
> Professor, Information Systems<br>
> San Francisco State University<br>
> <a href="http://verma.sfsu.edu/" target="_blank">http://verma.sfsu.edu/</a><br>
> <a href="http://commons.sfsu.edu/" target="_blank">http://commons.sfsu.edu/</a><br>
> <a href="http://olpcsf.org/" target="_blank">http://olpcsf.org/</a><br>
> <a href="http://olpcjamaica.org.jm/" target="_blank">http://olpcjamaica.org.jm/</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Sun, 6 Oct 2013 15:29:10 -0400<br>
> From: Walter Bender <<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>><br>
> To: Sameer Verma <<a href="mailto:sverma@sfsu.edu">sverma@sfsu.edu</a>><br>
> Cc: Devel's in the Details <<a href="mailto:devel@lists.laptop.org">devel@lists.laptop.org</a>>, John Gilmore<br>
> <<a href="mailto:gnu@toad.com">gnu@toad.com</a>><br>
> Subject: Re: Android on the XO-4<br>
> Message-ID:<br>
> <CADf7C8tYNdp-Hv-RXHo54X=<a href="mailto:9cSForWQq33Dgy%2BrLN03wSExQXw@mail.gmail.com">9cSForWQq33Dgy+rLN03wSExQXw@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1<br>
><br>
> Not sure this helps us get around the Marvel bottleneck, but worth<br>
> investigating.<br>
><br>
> -walter<br>
><br>
>> On Sun, Oct 6, 2013 at 2:03 PM, Sameer Verma <<a href="mailto:sverma@sfsu.edu">sverma@sfsu.edu</a>> wrote:<br>
>> I was at the Internet Archive for some work on Pathagar<br>
>> (<a href="https://github.com/PathagarBooks/pathagar" target="_blank">https://github.com/PathagarBooks/pathagar</a>). Also there that afternoon<br>
>> was John Gilmore (cc'd). We got to talking about the XO-4, Android,<br>
>> HTML5, etc. A bit of doodling on Physics, and John put together a two<br>
>> cylinder engine, complete with a rocker arm :-) He also suggested the<br>
>> possibility of CyanogenMod on the XO-4 as a starting point.<br>
>><br>
>> If there is any interest in this, please submit a proposal for the<br>
>> upcoming OLPC SF summit<br>
>> <a href="http://www.olpcsf.org/CommunitySummit2013/proposal" target="_blank">http://www.olpcsf.org/CommunitySummit2013/proposal</a><br>
>><br>
>> John,<br>
>><br>
>> If you are in town Oct 18-20, we'd love to have you there.<br>
>> <a href="http://olpcsf.org/summit" target="_blank">http://olpcsf.org/summit</a><br>
>><br>
>> cheers,<br>
>> Sameer<br>
>> --<br>
>> Sameer Verma, Ph.D.<br>
>> Professor, Information Systems<br>
>> San Francisco State University<br>
>> <a href="http://verma.sfsu.edu/" target="_blank">http://verma.sfsu.edu/</a><br>
>> <a href="http://commons.sfsu.edu/" target="_blank">http://commons.sfsu.edu/</a><br>
>> <a href="http://olpcsf.org/" target="_blank">http://olpcsf.org/</a><br>
>> <a href="http://olpcjamaica.org.jm/" target="_blank">http://olpcjamaica.org.jm/</a><br>
>> _______________________________________________<br>
>> Devel mailing list<br>
>> <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
>> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
><br>
><br>
><br>
> --<br>
> Walter Bender<br>
> Sugar Labs<br>
> <a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Mon, 7 Oct 2013 10:54:45 +1100<br>
> From: James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>><br>
> To: Yioryos Asprobounitis <<a href="mailto:mavrothal@yahoo.com">mavrothal@yahoo.com</a>><br>
> Cc: OLPC Devel <<a href="mailto:devel@lists.laptop.org">devel@lists.laptop.org</a>><br>
> Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4<br>
> Message-ID: <<a href="mailto:20131006235445.GC19250@us.netrek.org">20131006235445.GC19250@us.netrek.org</a>><br>
> Content-Type: text/plain; charset=iso-8859-1<br>
><br>
> On Fri, Oct 04, 2013 at 10:32:17PM -0700, Yioryos Asprobounitis wrote:<br>
>>> Does not boot if the files are unpacked onto internal eMMC and no<br>
>><br>
>>> external SD card is present.? Workaround: edit olpc.fth to ensure<br>
>>> mmcblk0 is used regardless.<br>
>> Thanks for the suggestion.<br>
>> However, we do not want to affect the original XO OS.<br>
><br>
> Don't worry about that.<br>
><br>
> 1. for laptops in deployments where this is important, the laptops<br>
> are locked and won't be able to install your build,<br>
><br>
> 2. the OLPC OS is very easily reinstalled, insert USB drive, hold<br>
> down four keys, press power button,<br>
><br>
> 3. external media such as SD card and USB drives are not always<br>
> available, but internal media is always available,<br>
><br>
>> That is also why we do not provide zd images that would be easier to<br>
>> install. People that want it in the internal eMMC? should know how<br>
>> to do it too ;)<br>
><br>
> For people who want to try your build, you have made it harder for<br>
> them, for (in my opinion) no good reason.<br>
><br>
> You need not use zd images. A simple Forth script would do fine.<br>
><br>
> ok d# 4096 fat32-partition int<br>
> ok copy u:\fd-arm.sfs int:\fd-arm.sfs<br>
> ok mkdir int:\boot<br>
> ok copy u:\boot\initrd.4 int:\boot\initrd.4<br>
> ok copy u:\boot\vmlinuz.4 int:\boot\vmlinuz.4<br>
> ok copy u:\boot\olpc.fth int:\boot\olpc.fth<br>
> ok bye<br>
><br>
> Can also copy out members from within .zip file using Open Firmware.<br>
><br>
> If you wanted to set up a barrier to booting from internal storage,<br>
> there are probably more logical methods.<br>
><br>
> --<br>
> James Cameron<br>
> <a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 4<br>
> Date: Sun, 6 Oct 2013 21:34:51 -0700 (PDT)<br>
> From: Yioryos Asprobounitis <<a href="mailto:mavrothal@yahoo.com">mavrothal@yahoo.com</a>><br>
> To: James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>><br>
> Cc: OLPC Devel <<a href="mailto:devel@lists.laptop.org">devel@lists.laptop.org</a>><br>
> Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4<br>
> Message-ID:<br>
> <<a href="mailto:1381120491.16660.YahooMailNeo@web163405.mail.gq1.yahoo.com">1381120491.16660.YahooMailNeo@web163405.mail.gq1.yahoo.com</a>><br>
> Content-Type: text/plain; charset=iso-8859-1<br>
><br>
><br>
>> 3.? external media such as SD card and USB drives are not always<br>
>> available, but internal media is always available,<br>
>><br>
>>> That is also why we do not provide zd images that would be easier to<br>
>>> install.? People that want it in the internal eMMC? should know how<br>
>>> to do it too ;)<br>
>><br>
>> For people who want to try your build, you have made it harder for<br>
>> them, for (in my opinion) no good reason.<br>
>><br>
>> You need not use zd images.? A simple Forth script would do fine.<br>
>><br>
>> ok d# 4096 fat32-partition int<br>
>> ok copy u:\fd-arm.sfs int:\fd-arm.sfs<br>
>> ok mkdir int:\boot<br>
>> ok copy u:\boot\initrd.4 int:\boot\initrd.4<br>
>> ok copy u:\boot\vmlinuz.4 int:\boot\vmlinuz.4<br>
>> ok copy u:\boot\olpc.fth int:\boot\olpc.fth<br>
>> ok bye<br>
><br>
> Thanks you for the script.<br>
> However this would imply that you already<br>
> have expanded the tarball in a stick and then you copy over instead of<br>
> just booting from it. So is hard to see how is any easier for the user.<br>
><br>
>> Can also copy out members from within .zip file using Open Firmware.<br>
><br>
> What would be interesting is to download<br>
> the the zipped file in the internal card and then have<br>
> forth do the rest. Is it possible to read the file from int:\home\olpc\Downloads\file.zip, keep it in RAM, format int and write back from RAM?<br>
><br>
> Though, come to think of it you may not need any of these. Could use alt-boot (assuming is empty) and existing partitions. Fatdog does not really care what else is in the partitions.<br>
> The challenge in this case is the fatdog-xo olpc.fth to know which device and setting we boot from and act accordingly in all possible scenarios.<br>
><br>
>> If you wanted to set up a barrier to booting from internal storage,<br>
>> there are probably more logical methods.<br>
><br>
> Suggestions are welcome as always ;)<br>
> Best<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 5<br>
> Date: Mon, 7 Oct 2013 17:05:54 +1100<br>
> From: James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>><br>
> To: Yioryos Asprobounitis <<a href="mailto:mavrothal@yahoo.com">mavrothal@yahoo.com</a>><br>
> Cc: OLPC Devel <<a href="mailto:devel@lists.laptop.org">devel@lists.laptop.org</a>><br>
> Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4<br>
> Message-ID: <<a href="mailto:20131007060554.GG19250@us.netrek.org">20131007060554.GG19250@us.netrek.org</a>><br>
> Content-Type: text/plain; charset=iso-8859-1<br>
><br>
> On Sun, Oct 06, 2013 at 09:34:51PM -0700, Yioryos Asprobounitis wrote:<br>
>><br>
>>> 3.? external media such as SD card and USB drives are not always<br>
>>> available, but internal media is always available,<br>
>>><br>
>>>> That is also why we do not provide zd images that would be easier to<br>
>>>> install.? People that want it in the internal eMMC? should know how<br>
>>>> to do it too ;)<br>
>>><br>
>>> For people who want to try your build, you have made it harder for<br>
>>> them, for (in my opinion) no good reason.<br>
>>><br>
>>> You need not use zd images.? A simple Forth script would do fine.<br>
>>><br>
>>> ok d# 4096 fat32-partition int<br>
>>> ok copy u:\fd-arm.sfs int:\fd-arm.sfs<br>
>>> ok mkdir int:\boot<br>
>>> ok copy u:\boot\initrd.4 int:\boot\initrd.4<br>
>>> ok copy u:\boot\vmlinuz.4 int:\boot\vmlinuz.4<br>
>>> ok copy u:\boot\olpc.fth int:\boot\olpc.fth<br>
>>> ok bye<br>
>><br>
>> Thanks you for the script.<br>
>> However this would imply that you already<br>
>> have expanded the tarball in a stick and then you copy over instead of<br>
>> just booting from it. So is hard to see how is any easier for the<br>
>> user.<br>
><br>
> Yes, because you used a container format with no firmware support.<br>
> Why didn't you use .zip?<br>
><br>
>>> Can also copy out members from within .zip file using Open Firmware.<br>
>><br>
>> What would be interesting is to download<br>
>> the the zipped file in the internal card and then have<br>
>> forth do the rest. Is it possible to read the file from<br>
>> int:\home\olpc\Downloads\file.zip, keep it in RAM, format int and<br>
>> write back from RAM?<br>
><br>
> The versioned filesystem of OLPC OS makes this impractical.<br>
><br>
>> Though, come to think of it you may not need any of these. Could use alt-boot (assuming is empty) and existing partitions. Fatdog does not really care what else is in the partitions.<br>
>> The challenge in this case is the fatdog-xo olpc.fth to know which device and setting we boot from and act accordingly in all possible scenarios.<br>
>><br>
>>> If you wanted to set up a barrier to booting from internal storage,<br>
>>> there are probably more logical methods.<br>
>><br>
>> Suggestions are welcome as always ;)<br>
><br>
> Detecting that olpc.fth was loaded from internal storage and then<br>
> terminating with a message is probably more appropriate.<br>
><br>
> --<br>
> James Cameron<br>
> <a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
><br>
><br>
> End of Devel Digest, Vol 92, Issue 5<br>
> ************************************<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</blockquote></div><br></div>