<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 4, 2014 at 11:27 AM, eas lab <span dir="ltr"><<a href="mailto:lab.eas@gmail.com" target="_blank">lab.eas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When will we have ETHO running on ARM, eg. rPi?</blockquote><div><br></div><div>This is a recurring comment (in most open systems discussions) with at least a couple of facets:</div><div><br></div><div> - Some people in the community may have the knowledge but not the interest or time to do the work</div>
<div> - Some people in the community may question the value of the work</div><div> - The set of people who want it and the set of people who can do it don't always overlap</div><div><br></div><div>I think the best way to tackle this is to look at the problem differently. How can we:</div>
<div><br></div><div> - Make the barriers to porting easier</div><div> - Reduce the cost or improve the return on investment for doing a port</div><div> - Grow the number of people who can facilitate a port</div><div><br></div>
<div>This is where I was extremely excited about the virtual machine. Though it's certainly not native, it is a stepping stone. If the port is mainly to drive the cost of the hardware down: done. Porting will always be a giant pain, and letting Some Other Community deal with the Driver of the Day is a blessing. Finding easier ways to leverage someone else's drivers for your target hardware may be difficult to accomplish on the outset but then may greatly facilitate future or alternative ports.</div>
<div><br></div><div>I think the VM is a stepping stone to that, and adding functionality to the VM is something that may be within the wheelhouse of more members of the community than a straight port.</div><div><br></div>
<div>-Jack</div></div></div></div>