On 10/21/2014 06:48 PM, Nikolay Dimitrov wrote:
Hi Denis,
On 10/22/2014 02:10 AM, Denis Laroche wrote:
After posting it crossed my mind to look at /proc/config.gz of the
Debian kernel and I was then able to make it work. I added the
THERMAL configuration variables you posted — thanks!
On 10/20/2014 04:01 AM, Denis Laroche wrote:
Hi all,
I'm running linux-yocto 3.14 on a BeagleBone Black.
I built cpufrequtils from meta-oe and set the kernel options to
activate CPU frequency scaling, with no success. /proc/config.gz shows
that the kernel config options are set, but there's
On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot p...@pabigot.com wrote:
First, some yak shaving:
If something goes wrong with linux-yocto's do_patch, it prints:
| ERROR. Could not apply patches for beaglebone.
|Patch failures can
On 08/29/2014 03:02 PM, Bruce Ashfield wrote:
On 14-08-29 03:31 PM, Peter A. Bigot wrote:
The point is that issuing a mv like:
mv $checkpoint_dir .$checkpoint_dir
without ensuring that the value of the variable doesn't contain path
components is fragile. I'm not really clear
On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot p...@pabigot.com wrote:
Now: What goes wrong with do_patch for me ultimately turns out to be
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5090 biting me again a
year after I filed and forgot
I've just returned to Yocto development, and am using Ubunto 12.04
64-bit with commit 8e05d5e at the head of poky's daisy branch, building
for core-image-base for MACHINE=beaglebone, testing on a Beaglebone
Black rev A5C.
The resulting image failed to boot, hanging after printing Starting
kernel
On 07/11/2014 08:48 AM, Bruce Ashfield wrote:
On 14-07-11 09:00 AM, Peter A. Bigot wrote:
When I replace /boot/uImage on the SD card with the ones corresponding
to built Image files with size 11223252 (0xab40d4) or smaller, the boot
succeeds as shown below. With uImage corresponding to Image
wrote:
On 13-08-31 12:07 PM, Peter A. Bigot wrote:
Let's start by defining terms that I think don't exist or aren't used
consistently. In what follows:
Some of what you may be missing is in the kernel architecture manuals,
which I wrote ages ago .. and which we subsequently moved to a harder
In my attempt to figure out how hardware.cfg is implicitly located and
applied, and how to provide one in a recipe-space BSP description, I
searched for hardware.cfg throughout poky and found the string only in
these extremely bizarre files:
llc[291]$ ls -l
