<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2013/11/13 Miguel Angel Ochoa Rodriguez <span dir="ltr"><<a href="mailto:maochoa@tecnipyme.com" target="_blank">maochoa@tecnipyme.com</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">
<div>>- In event of failure to implement GPIO , I noticed that the photos of<br>
>The first prototype boards last is eliminated auxiliary bus had on top<br>
<br>
<br>
>The Bus on top is a 44 pin header, 30pins are RGB/TTL, 8 are GPIO, 2 are I2C, 2 are RX/Tx, and the last 2 are 5VDC and >GND.<br>
<br>
</div>Are you sure in the last EOMA68 A20 Boards have this conector?¿?<br>
<br>
In the news Photos of working examples in april and may dont see this conector<br>
<a href="http://rhombus-tech.net/allwinner_a10/news/" target="_blank">http://rhombus-tech.net/allwinner_a10/news/</a><br>
<br>
<br>
In the case of A20 plate actually incorporates an auxiliary bus 44pins.<br>
<br>
It would be possible to extend or modify the bus to enter the i2s??<br></blockquote><div><br></div><div>Extending the spec to include i2s or s/p diff requires the SoC to provide either. Or additional hardware needs to be added to the already cramped EOMA card. Regardles of the SoC used AllWinner Axx, Freescale iMX.x, <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">
<br>
If I'm right in the project OLINUXINO implemented several lines of cpu<br>
to the same pin expansion connectors with a choice of system function<br>
pin<br>
<br>
<a href="https://github.com/OLIMEX/OLINUXINO" target="_blank">https://github.com/OLIMEX/OLINUXINO</a><br>
<br>
2013/11/13 luke.leighton <<a href="mailto:luke.leighton@gmail.com" target="_blank">luke.leighton@gmail.com</a>>:<br>
<div>>> Modifying the specification at this point in the EOMA68 seems unlikely,<br>
><br>
> not a chance. audio was one of the first things that was eliminated<br>
> from putting out over the 68 pins due to there being no clear common<br>
> audio standard. it is left to implementors to decide what ICs to<br>
> place on the I/O board, USB audio being the most sensible and<br>
> self-contained option.<br>
><br>
<br>
</div>For us this would be the second option since we have found that using<br>
converters usb light generated synchronization delays in the video /<br>
audio. that must be corrected through the player (XBMC - MPlayer).<br></blockquote><div><br></div><div>Both PulseAudio has audio delay options for syncing multiple outputs like network linked pulse audio devices (Like Logitech SqueezeBox, Sonos, etc). I believe ALSA (drivers) also has(have) delay parameters. Obviously because expecting every sound source, eg. Mplayer, FireFox, Audacity, VLC, etc., to sync them selfs is unthinkable.<br>
<br><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">
<br>
By contrast, in the tests we've done with CPU integrated SPDIF not <br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">have these delays. (Important in case of decoding DTS or DOLBY
</blockquote><div><br><div>S/P Diff does not support DTS-HD/Dolby true HD. Max 192Mhz/24Bit is not enough bandwith. And a lot of HW only accepts<br></div><div>i2s should be capable but only if all component support such a high bitrate. I think in i2s no min max bandwith is specified<br>
</div><div>HDMI audio does support DTS-HD/Dolby true HD. <br><br></div><div>The only usefull/low cost standard available left is USB. <br><br></div><div>Most audiophiles prefer USB because, among the above, it lets you do DAC outside the digital LF and HF noise environment a computer is.<br>
</div><br></div><div>Yes A/V sync is a b*tch but nothing new. Usually the regular PCI/SoC audio drivers already contain the correct timings because the position of all components is sort of fixed. Even in windows. With USB the infrastucture tends to be a bit more differential, controllers, hubs, same audio chips used in different config and pcb layouts.<br>
<br></div><div>And thus requires a bit more tinkering.<br><br></div><div>Good luck!<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><div>
_______________________________________________<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" target="_blank">http://lists.phcomp.co.uk/mailman/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><br>
</div></div></blockquote></div><br></div></div>