<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-01-09 0:08 GMT+01:00 peter green <span dir="ltr"><<a href="mailto:plugwash@p10link.net" target="_blank">plugwash@p10link.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 08/01/17 12:58, Luke Kenneth Casson Leighton wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Thu, Jan 5, 2017 at 9:24 PM, Luke Kenneth Casson Leighton<br>
<<a href="mailto:lkcl@lkcl.net" target="_blank">lkcl@lkcl.net</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
i'm not letting you off the hook here after you said that EOMA68's<br>
interfaces are "crippled", peter.<br>
</blockquote>
ok, so can you see what i did, peter? you laid down a challenge (to<br>
do better)... and after three days, you've not responded. you<br>
*provisionally* described an alternative standard... but did not<br>
follow through.<br>
<br>
*that's* what makes the difference, here. it's *not enough* to say<br>
"the standard you came up with is rubbish", you have to *follow<br>
through*, and if you can't follow through then it's.... you know what<br>
i'm trying to say?<br>
</blockquote></span>
The compromises you made are a result of your goals. You wanted a standard that could be implemented with virtually any cheap SoC. That basically forced you into the decisions to use USB and parallel RGB.<br>
<br>
Unfortunately USB has a reputation for poor performance and reliability. Some of this is possibly the fault of the USB standards themselves, some is a result of crappy implementations.<br></blockquote><div><br></div><div>Examples please.</div><div><br></div><div>If USB had such a bad track record then why is it the most used peripheral interface? </div><div><br></div><div>And which part of the USB standard? The physical interface or the communication protocols?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Intel has different goals, their job is to make something that takes best advantage of their own current and future products. EOMA68 does not do that, it drags it down to the lowest common denominator. As such I believe that by adopting EOMA68 Intel would be crippling their product. I gave some examples of interfaces I think Intel should include that were unsuitable for EOMA68.<br></blockquote><div><br></div><div>The lowest common denominator is what's going to get this running. Everyone can join in with almost everything. You could even create a EOMA Card with a beefy Microcontroller.</div><div><br></div><div>Once everyone is in, new interfaces can be chosen/developed for the next version/type.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I don't know exactly what Interfaces it would be best for Intel to include, that would require knowing both full details of the chips they plan to use in their current cards as well as their future roadmaps (if they have something on their SoCs today but plan to drop it in the future it would be stupid for them to put it on their compute cards).</blockquote><div><br></div><div>Intel could force a "new" standard by flooding or hyping the market. That would require every other vendor to follow the Intel route.</div><div><br></div><div>For other company's to follow that usually comes in two tracks:</div><div>1. Intel has made a success en the they "chime" in on the succes</div><div>2. Intel actively recruits "partners" to co-develop products </div><div><br></div><div>But I don't think so. Intel is desperate to find new grounds and are shooting with hail. It'll surprise me if they are still around after ten years.</div><div><br></div><div>1. Desktop and Laptop markets are shrinking.</div><div>2. Server market is shifting to better Power/Watt ratios. ARM is gaing. The market is opening again to other CPU architectures becaus of Saas offerings.</div><div>3. Computing market is shifting to GPU's.</div><div>4. Intel failed at the mobile market. To power hungry/To late.</div><div>5. Intel failed at the IoT market. To power hungry/To late.</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" rel="noreferrer" target="_blank">http://lists.phcomp.co.uk/mail<wbr>man/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a></div></div></blockquote></div><br></div></div>