From: "Peter A. Bigot" <pab@pabigot.com>
To: Denys Dmytriyenko <denys@ti.com>,
Mikhail Zakharov <mikhail.zakharov@cognitivesystems.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: poor performance of OpenEmbedded on, BeagleBoneBlack compared to Debian
Date: Thu, 04 Sep 2014 10:37:24 -0500 [thread overview]
Message-ID: <54088734.1090204@pabigot.com> (raw)
In-Reply-To: <20140904150022.GD18620@edge>
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 <pab@pabigot.com> 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
next prev parent reply other threads:[~2014-09-04 15:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 14:50 poor performance of OpenEmbedded on, BeagleBoneBlack compared to Debian Mikhail Zakharov
2014-09-04 15:00 ` Denys Dmytriyenko
2014-09-04 15:37 ` Peter A. Bigot [this message]
2014-09-04 15:41 ` Peter A. Bigot
2014-09-04 17:50 ` Peter A. Bigot
2014-09-04 15:48 ` Denys Dmytriyenko
2014-09-04 15:55 ` Robert Nelson
2014-09-04 18:10 ` Denys Dmytriyenko
2014-09-04 19:03 ` Robert Nelson
2014-09-04 19:09 ` Denys Dmytriyenko
2014-09-04 19:04 ` Peter A. Bigot
2014-09-04 19:07 ` Robert Nelson
2014-09-04 19:09 ` Robert Nelson
2014-09-04 19:41 ` Denys Dmytriyenko
2014-09-04 15:55 ` Peter A. Bigot
2014-09-04 19:48 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2014-09-04 1:59 poor performance of OpenEmbedded on " Peter A. Bigot
2014-09-04 2:46 ` Robert Nelson
2014-09-04 10:46 ` Peter A. Bigot
2014-09-04 5:39 ` Khem Raj
2014-09-04 10:55 ` Peter A. Bigot
2014-09-04 12:33 ` Dmytriyenko, Denys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54088734.1090204@pabigot.com \
--to=pab@pabigot.com \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=mikhail.zakharov@cognitivesystems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.