<div dir="ltr">Got it.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 18, 2014 at 10:55 AM, Gary Thomas <span dir="ltr"><<a href="mailto:gary@mlbassoc.com" target="_blank">gary@mlbassoc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 2014-03-18 11:49, Rick Bianchi wrote:<br>
> Should have noted, that the date and time reset on every reboot?<br>
<br>
</div>Unless you have a battery backed up clock device, e.g. Dallas RTC,<br>
this will happen. If you shut your Yocto system down properly, e.g.<br>
using '# reboot', it will keep track of when you shut down and then<br>
set the clock to that time when you reboot. Without a true RTC, there's<br>
little else that it can do unless you run NTP and get the time from some<br>
external server.<br>
<div class=""><br>
> On Tue, Mar 18, 2014 at 10:48 AM, Rick Bianchi <<a href="mailto:bianchirickkutta@gmail.com">bianchirickkutta@gmail.com</a> <mailto:<a href="mailto:bianchirickkutta@gmail.com">bianchirickkutta@gmail.com</a>>> wrote:<br>
><br>
> Gary,<br>
> I noticed during the make the it was complaining about the date being in the future; I checked and sure thing the date and time were bit off, about 14 years. I set it to the<br>
> correct time with "date --set="18 MARCH 2014 10:32:00" and the build completed in under 10 mins.<br>
><br>
><br>
</div><div class="">> On Fri, Mar 14, 2014 at 3:16 PM, Gary Thomas <<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>> wrote:<br>
><br>
> On 2014-03-14 08:49, Rick Bianchi wrote:<br>
> > If I have time today I will try to reproduce your results. If not, I will get to it first thing next week and post my result.<br>
><br>
> One thing I forgot to point out is I used the identical kernel+modules for<br>
> both setups. I would be interested to see if that makes any difference for<br>
> you. I can't fully test it as my board doesn't have a Linaro kernel.<br>
><br>
> So there are four combinations - I only tried the first two:<br>
> Yocto kernel + Yocto rootfs<br>
> Yocto kernel + Linaro rootfs<br>
> Linaro kernel + Yocto rootfs<br>
> Linaro kernel + Linaro rootfs<br>
><br>
</div><div class="">> > On Fri, Mar 14, 2014 at 7:38 AM, Gary Thomas <<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>>> wrote:<br>
> ><br>
> > On 2014-03-12 13:11, Rick Bianchi wrote:<br>
> > > usbip from /usr/src/kernel/drivers/staging/usbip<br>
> ><br>
> > I finally managed to make this comparison. I did this by taking my Poky/Yocto<br>
> > built system for a i.MX6 system (ARM Cortex-A9) and replaced the rootfs with<br>
> > one for the Gumstix Overo (linaro). The results were nothing like yours, so<br>
> > it's a bit confusing.<br>
> ><br>
> > I actually built an entire Linux kernel - not just the one directory you mentioned.<br>
> ><br>
> > Poky/Yocto - 37 minutes<br>
> > Linaro - 48 minutes<br>
> ><br>
> > There is some flex in these numbers as they were on different [brand] SD cards, etc,<br>
> > but I sure did not see the "5 minutes for Linaro vs 24 hours on Yocto" that you reported.<br>
> ><br>
> > Perhaps the only thing I did differently was I added the SDK tools to my Yocto system<br>
> > using these meta-packages instead of the list you used.<br>
> > packagegroup-core-sdk packagegroup-core-standalone-sdk-target<br>
> ><br>
> > You might try that to see if it makes any difference.<br>
> ><br>
> > n.b. part of what took me so long to get these results is I was trying to run this test<br>
> > on something closer to your Overo board. I have an older OMAP DM3730 board here that I<br>
> > tried to do these same steps, but it was unstable and I could not get the Linaro based<br>
> > file system to work at all. Very strange. In any case, I think the comparison I did get<br>
> > with the i.MX6 is valid.<br>
> ><br>
</div>> > > On Wed, Mar 12, 2014 at 11:44 AM, Gary Thomas <<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>><br>
<div class="">> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>>>> wrote:<br>
> > ><br>
> > > On 2014-03-12 10:09, Rick Bianchi wrote:<br>
> > > > I completely agree with regards to the comparison, but I have compiled the same exact source on the same target (arm) and it only took 5 minutes when running the Linaro image.<br>
> > > ><br>
> > > > To clarify, the only difference is the build, one is Linaro (took 5 minutes to compile source on the target) and the other Yocto (took almost 24 hours to compile source on the target).<br>
> > ><br>
> > > Sorry, I missed that this was on the same hardware.<br>
> > ><br>
> > > What are you building? I'm going to try and duplicate this here<br>
> > > on hardware I have that's quite similar to your Gumstix board.<br>
> > ><br>
> > > ><br>
> > > > Is there something that I am missing?<br>
> > > ><br>
> > > ><br>
> > > > On Wed, Mar 12, 2014 at 8:28 AM, Gary Thomas <<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>><br>
</div>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>><br>
<div><div class="h5">> > <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a> <mailto:<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>>>>>> wrote:<br>
> > > ><br>
> > > > On 2014-03-12 09:15, Rick Bianchi wrote:<br>
> > > > ><br>
> > > > > I have the gumstix-console-image with the added packages below. When I compile on the target is take a very long time for it to complete, over 24 hours. I have compiled the same<br>
> > > > > code on the same target, but running Linaro image, and it only takes a few minutes. Is there another recipe that I need to add to the build to speed up compiling?<br>
> > > ><br>
> > > > Doubtful. The reason your build on the target takes so long is merely<br>
> > > > one of horsepower - that little ARM processor just doesn't have it, especially<br>
> > > > if you are comparing it to a typical desktop environment.<br>
> > > ><br>
> > > > > EXTRA_IMAGE_FEATURES += "dev-pkgs"<br>
> > > > > IMAGE_INSTALL_append =" autoconf"<br>
> > > > > IMAGE_INSTALL_append =" autofs"<br>
> > > > > IMAGE_INSTALL_append =" automake"<br>
> > > > > IMAGE_INSTALL_append =" ccache”<br>
> > > > > IMAGE_INSTALL_append =" chkconfig"<br>
> > > > > IMAGE_INSTALL_append =" dbus-glib"<br>
> > > > > IMAGE_INSTALL_append =" gcc"<br>
> > > > > IMAGE_INSTALL_append =" glib-2.0"<br>
> > > > > IMAGE_INSTALL_append =" glib-networking"<br>
> > > > > IMAGE_INSTALL_append =" glibmm"<br>
> > > > > IMAGE_INSTALL_append =" packagegroup-core-buildessential"<br>
> > > > > IMAGE_INSTALL_append =" pciutils"<br>
> > > > > IMAGE_INSTALL_append =" pkgconfig”<br>
> > > > > IMAGE_INSTALL_append =" python-scons"<br>
> > > > > IMAGE_INSTALL_append =" systemd-compat-units”<br>
> > > > > IMAGE_INSTALL_append =" sysfsutils"<br>
> > > > > IMAGE_INSTALL_append =" tcp-wrappers"<br>
> > > > > IMAGE_INSTALL_append =" usbutils"<br>
> > > > > IMAGE_INSTALL_append =" util-macros"<br>
> ><br>
> > --<br>
> > ------------------------------------------------------------<br>
> > Gary Thomas | Consulting for the<br>
> > MLB Associates | Embedded world<br>
> > ------------------------------------------------------------<br>
> > --<br>
> > _______________________________________________<br>
> > yocto mailing list<br>
</div></div>> > <a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a> <mailto:<a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a>> <mailto:<a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a> <mailto:<a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a>>><br>
<div class="HOEnZb"><div class="h5">> > <a href="https://lists.yoctoproject.org/listinfo/yocto" target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
><br>
> --<br>
> ------------------------------------------------------------<br>
> Gary Thomas | Consulting for the<br>
> MLB Associates | Embedded world<br>
> ------------------------------------------------------------<br>
> --<br>
> _______________________________________________<br>
> yocto mailing list<br>
> <a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a> <mailto:<a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a>><br>
> <a href="https://lists.yoctoproject.org/listinfo/yocto" target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
><br>
><br>
><br>
<br>
--<br>
------------------------------------------------------------<br>
Gary Thomas | Consulting for the<br>
MLB Associates | Embedded world<br>
------------------------------------------------------------<br>
</div></div></blockquote></div><br></div>