<div class="gmail_quote">On Fri, Jul 9, 2010 at 4:17 AM, Karl Goetz <span dir="ltr"><<a href="mailto:karl@kgoetz.id.au">karl@kgoetz.id.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, 8 Jul 2010 23:19:54 -0400<br>
Daniel Clark <<a href="mailto:dclark@pobox.com">dclark@pobox.com</a>> wrote:<br>
<br>
> FYI no code yet, but promises that may help the effort to get OpenEC<br>
> working on Lemote Yeeloong...<br>
<br>
</div>Interesting news.<br>
<div class="im"><br>
> The exception is because EnE has not released the low-level details on<br>
> the PS/2 interface in the KB3930, so there will be some code that is<br>
<br>
</div>Does anyone know what functionality is lost by this code being<br>
proprietary? (if we removed it).<br>
kk<br>
<div><div></div><div class="h5"><br>
> not available -- relative to the codebase this is a very small amount<br>
> of code. The GPL licensing exception will allow for linking against<br>
> this closed code. We're going to investigate ways to move away from<br>
> this code in the future. (As far as we're aware, this will make the<br>
> XO-1.75 the first laptop with open embedded controller code!)<br></div></div></blockquote><div><br></div><div>Sending to a lot of lists with people who might be interested, but for replies I'd suggest signing up for and then replying only to the <a href="http://lists.laptop.org/listinfo/openec">http://lists.laptop.org/listinfo/openec</a> list, which is very low-volume. Archives at <a href="http://lists.laptop.org/pipermail/openec/">http://lists.laptop.org/pipermail/openec/</a></div>
<div><br></div><div>FYI actual location of the code and some other interesting info. I'll also go update <a href="http://wiki.laptop.org/go/OpenEC">http://wiki.laptop.org/go/OpenEC</a> with this location as the location currently mentioned has really old code (2009). </div>
<div><br></div><div>Perhaps this will also be helpful with OpenEC on Lemote Yeeloong work (FSF donated a few Yeeloongs to people who wanted to work on that a while ago, but as far as I know there has not been a lot of progress there.)</div>
<div><br></div><div>cjb | djbclark: <a href="http://dev.laptop.org/git/users/rsmith/ec-1.75">http://dev.laptop.org/git/users/rsmith/ec-1.75</a> for all your openec needs</div><div>cjb | (it's actually the repo we're using to bring up the 1.75 right now)</div>
<div>dilinger | cjb: is this xo-1 EC minus battery code, or written from scratch?</div><div>cjb | dilinger: battery code's in there, AIUI</div><div>cjb | the patent was on the NiMH battery charging, and we don't use those batteries anymore, only LiFePO4</div>
<div>dilinger | cjb: awesome</div><div>dilinger | so is that imported into OFW now, or do you still build the EC separately?</div><div>cjb | on 1.75 they're more independent than before</div><div>cjb | they don't flash a new EC at the same time as flashing a new OFW</div>
<div>cjb | so they aren't built together</div><div>dilinger | interesting</div><div>cjb | OFW also isn't the first thing that runs anymore</div><div>cjb | the mmp2 has two cores, security processor and the main CPU (PJ4)</div>
<div>cjb | comes up in cforth on the SP, that loads from SPI into SRAM and releases the PJ4</div><div>cjb | the SP keeps running</div><div>cjb | which is neat because you can make it watch a GPIO/button</div><div>cjb | and if the PJ4 hangs, you hit that button, the SP takes over the serial port again, and it has full access to RAM and peripheral state for debugging</div>
<div>cjb | so there's an always-available method for getting dmesg after a crash</div><div>dilinger | SP continues running OFW the entire time?</div><div>dilinger | is it drawing full power, or is it some kind of low power mode (similar to the low power EC mode)?</div>
<div>cjb | (cforth, not OFW)</div><div>cjb | yeah, I think it's drawing power </div><div>cjb | we'll have to work out how that's supposed to work later</div><div><br></div>--<br> \|/ Daniel JB Clark | Activist; Owner<br>
FREEDOM -+-> INCLUDED ~ <a href="http://freedomincluded.com/" target="_blank">http://freedomincluded.com</a> <br><div> /|\ Free Software respecting hardware </div></div><br>