From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 93189E0076C; Thu, 4 Sep 2014 08:37:34 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [173.201.193.231 listed in list.dnswl.org] Received: from p3plsmtpa09-02.prod.phx3.secureserver.net (p3plsmtpa09-02.prod.phx3.secureserver.net [173.201.193.231]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 588BCE006EF for ; Thu, 4 Sep 2014 08:37:27 -0700 (PDT) Received: from [192.168.65.10] ([66.41.60.82]) by p3plsmtpa09-02.prod.phx3.secureserver.net with id n3dQ1o00P1mTNtu013dRl7; Thu, 04 Sep 2014 08:37:26 -0700 Message-ID: <54088734.1090204@pabigot.com> Date: Thu, 04 Sep 2014 10:37:24 -0500 From: "Peter A. Bigot" Organization: Peter Bigot Consulting, LLC User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Denys Dmytriyenko , Mikhail Zakharov References: <20140904150022.GD18620@edge> In-Reply-To: <20140904150022.GD18620@edge> Cc: "meta-ti@yoctoproject.org" Subject: Re: poor performance of OpenEmbedded on, BeagleBoneBlack compared to Debian X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2014 15:37:34 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 09/04/2014 10:00 AM, Denys Dmytriyenko wrote: > On Thu, Sep 04, 2014 at 02:50:03PM +0000, Mikhail Zakharov wrote: >> On Wed, Sep 3, 2014 at 8:59 PM, Peter A. Bigot wrote: >> >>> One anomaly I've found is the CPU frequency range. On debian we have: >>> >>> debian@beaglebone:~$ cat >>> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies >>> 300000 600000 800000 1000000 >>> >>> while on OE we have: >>> >>> root@beaglebone:~# cat >>> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies >>> 300000 600000 720000 800000 >> Stock yocto-bsp is missing a few things that can be found in Robert >> Nelson's patchset for 3.14 linux kernel. >> >> There are lots of other functionality that is missing from yocto-bsp >> kernel for Beaglebone. I suggest you take at the following repos and >> scavenge for what you need :P > First of all, this is meta-ti mailing list for the corresponding BSP. That's > what Peter was asking for, comparing to Robert's Debian and Yocto reference > BSPs, not the other way around. > > Second, Yocto reference BSP is that way for a reason - it's a reference BSP > done with pure mainline kernel and u-boot components w/o any patching on top. > That's its entire purpose. For anything else special, including performance > tweaks, there are other BSPs available. If there is an issue with performance > in meta-ti, we'll investigate it and try to match with Robert's BSP. Yes, at this time meta-ti's BSP performs as well as I've seen any OE-based system, and gets several things right that meta-yocto-bsp does not (and one thing wrong that meta-yocto-bsp gets right, I think; still investigating, will follow-up when I'm sure). I've also verified that performance with a native gcc 4.9.1 build on BeagleBone with hard float is poor, so it's not due to the way OE builds gcc. I have several competing hypotheses to test. But I'm still looking for a way to set the CPU frequency to the higher values supported on Beaglebone Black. I had hoped meta-ti's would be able to do that, since it has bone vs boneblack device trees and u-boot detection. Any hints where to look for clock settings? Peter