<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>I have spent some (frustrating) time on this. The good news is that
<A title=https://github.com/jmontleon/fedora-20-cubox-i4pro-binary
href="https://github.com/jmontleon/fedora-20-cubox-i4pro-binary">https://github.com/jmontleon/fedora-20-cubox-i4pro-binary</A>
actually works including the wifi and clock, I think (ntpd masks the
problem). (the bad news is that it is fc20 not fc18.) I haven’t
tried esata yet. I agree we should get to fc20 at some point, but I was
hoping to get a proof on 18 1st. Santi mentioned a few things not working
on 20, but I don’t know what his status is now. Anyway, if you install 20
and leave things out of ansible that don’t work, I think you will more or less
get a schoolserver.</DIV>
<DIV> </DIV>
<DIV>I am as I write trying to get <A
title=https://github.com/linux4kix/linux-linaro-stable-mx6
href="https://github.com/linux4kix/linux-linaro-stable-mx6">https://github.com/linux4kix/linux-linaro-stable-mx6</A>
to work. My first attempt was a hail Mary in which I simply copied the
3.14 kernel files and dtb directory from fc20 into fc18 – panic.</DIV>
<DIV> </DIV>
<DIV>I then tried to cross-compile from the latter git repo on x64, but the
toolchain must be wrong as it fails to make. (I don’t find
arm-linux-gnueabi for fedora only <FONT
style="BACKGROUND-COLOR: #f9f9f9">arm-linux-gnu</FONT>, which didn’t
work.)</DIV>
<DIV> </DIV>
<DIV>I am now trying a native compile of <A
title=https://github.com/linux4kix/linux-linaro-stable-mx6
style='href: "https://github.com/linux4kix/linux-linaro-stable-mx6"'>https://github.com/linux4kix/linux-linaro-stable-mx6</A>
on the cubox-i-f18-hardfp.img and will then try to create a fresh install with
the new SPF and uboot files and that kernel.</DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">Tim</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=georgejhunt@gmail.com
href="mailto:georgejhunt@gmail.com">George Hunt</A> </DIV>
<DIV><B>Sent:</B> Tuesday, March 11, 2014 3:33 PM</DIV>
<DIV><B>To:</B> <A title=xsce-devel@googlegroups.com
href="mailto:xsce-devel@googlegroups.com">xsce-devel</A> </DIV>
<DIV><B>Cc:</B> <A title=server-devel@lists.laptop.org
href="mailto:server-devel@lists.laptop.org">server-devel@lists.laptop.org</A>
</DIV>
<DIV><B>Subject:</B> Re: [XSCE] cubox wifi</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV dir=ltr>
<DIV>Tim, Curt,</DIV>
<DIV> </DIV>I'm almost ready to start playing around with cubox -- at this
point, just trying to remember where we're at. Have either of you started?
<DIV> </DIV>
<DIV>Regarding the issue of FC18, vs FC20 that Tim raised with Jon, I think it's
strategic for us to move forward on FC20. We can disable stuff in XSCE
that stalls the ansible install.</DIV>
<DIV> </DIV>
<DIV>Tim, can you refresh my memory on the current issues encountered getting
XSCE on FC20? Do you think that changes to get XSCE to run on FC20 are doable,
if not for 5.1 then 6.<BR>
<DIV>
<DIV>The readme, at <A
href="https://github.com/jmontleon/fedora-20-cubox-i4pro">https://github.com/jmontleon/fedora-20-cubox-i4pro</A>,
changed 14 days ago, looks to be something I could follow.</DIV></DIV></DIV>
<DIV><BR> </DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Tue, Feb 25, 2014 at 4:17 PM, Jon Nettleton <SPAN
dir=ltr><<A href="mailto:jon.nettleton@gmail.com"
target=_blank>jon.nettleton@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I
am not 100% sure what is enabled and what isn't but I
believe<BR>wifi/esata/bluetooth are all working.<BR><BR><A
href="https://github.com/jmontleon/fedora-20-cubox-i4pro"
target=_blank>https://github.com/jmontleon/fedora-20-cubox-i4pro</A><BR><A
href="https://github.com/jmontleon/fedora-20-cubox-i4pro-binary"
target=_blank>https://github.com/jmontleon/fedora-20-cubox-i4pro-binary</A><BR><BR>Should
be a good start. That is a mainline kernel not my patched 3.10<BR>kernel
so there are some things that aren't supported but those are<BR>mostly
multimedia/graphics related.<BR><SPAN class=HOEnZb><FONT
color=#888888><BR>-Jon<BR></FONT></SPAN>
<DIV class=HOEnZb>
<DIV class=h5><BR>On Tue, Feb 25, 2014 at 3:46 PM, Jon Nettleton <<A
href="mailto:jon.nettleton@gmail.com">jon.nettleton@gmail.com</A>>
wrote:<BR>> George,<BR>><BR>> I agree, but the device-tree cookbook
description is not as simple as<BR>> the legacy way of setting up a new
kernel. There are lots of<BR>> variables that need to be taken into
account depending on the kernel<BR>> version, board version, u-boot version
OS etc. Writing a proper<BR>> cookbook is time I just don't
have. Hopefully one of the other<BR>> contributors will step up and
get it done.<BR>><BR>> -Jon<BR>><BR>> On Tue, Feb 25, 2014 at 3:43
PM, George Hunt <<A
href="mailto:georgejhunt@gmail.com">georgejhunt@gmail.com</A>>
wrote:<BR>>> Jon,<BR>>><BR>>> In the long run, (my opinion),
a cookbook description (similar to the<BR>>> solidrun link) of the
process would be more needed than a tarball. Your<BR>>> time, and
our education, has real value.<BR>>><BR>>><BR>>> On Tue, Feb
25, 2014 at 12:44 AM, Jon Nettleton <<A
href="mailto:jon.nettleton@gmail.com">jon.nettleton@gmail.com</A>><BR>>>
wrote:<BR>>>><BR>>>> George,<BR>>>><BR>>>>
Things have actually changed a bit as the new kernel is using the
new<BR>>>> device-tree based configuration. I will build you
guys a testing<BR>>>> kernel tarball and u-boot in a little
bit.<BR>>>><BR>>>> -Jon<BR>>>><BR>>>> On
Tue, Feb 25, 2014 at 12:18 AM, George Hunt <<A
href="mailto:georgejhunt@gmail.com">georgejhunt@gmail.com</A>><BR>>>>
wrote:<BR>>>> > Hi Jon,<BR>>>> ><BR>>>> >
Is it correct that I can follow the directions at:<BR>>>>
><BR>>>> ><BR>>>> ><BR>>>> > <A
href="http://imx.solid-run.com/wiki/index.php?title=Building_the_kernel_and_u-boot_for_the_CuBox-i_and_the_HummingBoard"
target=_blank>http://imx.solid-run.com/wiki/index.php?title=Building_the_kernel_and_u-boot_for_the_CuBox-i_and_the_HummingBoard</A><BR>>>>
><BR>>>> > with a clone from the github link you provided
at<BR>>>> > <A
href="https://github.com/linux4kix/linux-linaro-stable-mx6"
target=_blank>https://github.com/linux4kix/linux-linaro-stable-mx6</A>? Are
there any<BR>>>> > gotchas?<BR>>>> >
Recommendations?<BR>>>> ><BR>>>> > I forget the
details from one month/day to the next.<BR>>>> ><BR>>>>
><BR>>>> > On Mon, Feb 24, 2014 at 9:38 AM, Jon Nettleton
<<A
href="mailto:jon.nettleton@gmail.com">jon.nettleton@gmail.com</A>><BR>>>>
> wrote:<BR>>>> >><BR>>>> >> Finally out and
ready for use.<BR>>>> >><BR>>>> >> <A
href="https://github.com/linux4kix/linux-linaro-stable-mx6"
target=_blank>https://github.com/linux4kix/linux-linaro-stable-mx6</A><BR>>>>
>><BR>>>> >> All the hardware is functional at this
point. The wifi driver is a<BR>>>> >> bit chatty and
needs a bit more love for AP mode. Everything else<BR>>>>
>> from crypto to esata should be good to go.<BR>>>>
>><BR>>>> >> -Jon<BR>>>>
>><BR>>>> >> On Sun, Feb 23, 2014 at 5:28 PM, Jon
Nettleton<BR>>>> >> <<A
href="mailto:jon.nettleton@gmail.com">jon.nettleton@gmail.com</A>><BR>>>>
>> wrote:<BR>>>> >> > It was probably a UHS capable
card. We found some hardware design<BR>>>> >> >
problems that will need to be rectified to support UHS speeds for
the<BR>>>> >> > sdcard. For now we will be limiting
the card-slot to standard SD<BR>>>> >> >
high<BR>>>> >> > speed modes of 50Mhz which equates to
around 20MB/s<BR>>>> >> ><BR>>>> >> > On
Sun, Feb 23, 2014 at 5:12 PM, Tim Moody <<A
href="mailto:tim@timmoody.com">tim@timmoody.com</A>> wrote:<BR>>>>
>> >> sounds great. one thing I noticed in Haiti was that I
could not get<BR>>>> >> >> a<BR>>>> >>
>> 16G<BR>>>> >> >> sd card to be recognized.
is this expected or was it my card?<BR>>>> >>
>><BR>>>> >> >> Tim<BR>>>> >>
>> -----Original Message----- From: Jon Nettleton<BR>>>>
>> >> Sent: Sunday, February 23, 2014 11:03 AM<BR>>>>
>> >> To: xsce-devel<BR>>>> >> >> Cc: <A
href="mailto:server-devel@lists.laptop.org">server-devel@lists.laptop.org</A><BR>>>>
>> >> Subject: Re: [XSCE] cubox wifi<BR>>>> >>
>><BR>>>> >> >><BR>>>> >> >>
Tim,<BR>>>> >> >><BR>>>> >> >>
Actually the 3.10 kernel is done. The wifi driver is a
little<BR>>>> >> >> chatty<BR>>>> >>
>> and I will work on sorting that out but it is functional. I am
just<BR>>>> >> >> cleaning up the last few patches and
will be pushing the kernel for<BR>>>> >> >> initial
testing in a few hours.<BR>>>> >> >><BR>>>>
>> >> -Jon<BR>>>> >> >><BR>>>>
>> >> On Sat, Feb 22, 2014 at 5:34 PM, Tim Moody <<A
href="mailto:tim@timmoody.com">tim@timmoody.com</A>> wrote:<BR>>>>
>> >>><BR>>>> >> >>>
Jon,<BR>>>> >> >>><BR>>>> >>
>>> Can you (or anyone else) tell me where to find the drivers for
the<BR>>>> >> >>> cubox<BR>>>> >>
>>> wifi adapter you mentioned on the call on Tue.<BR>>>>
>> >>><BR>>>> >> >>>
Thanks,<BR>>>> >> >>><BR>>>> >>
>>> Tim<BR>>>> >> >><BR>>>> >>
>><BR>>>> ><BR>>>>
><BR>>><BR>>><BR></DIV></DIV></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV></DIV></DIV></BODY></HTML>