Thanks for the additional information. My entire expectation of how
linux-yocto metadata worked turns out to be wrong, but you've managed to
clear it up for me.
What I really wanted from linux-yocto was a way to isolate documented
kernel configuration fragments to share configuration data
On Sep 1, 2013, at 8:08 AM, Bruce Ashfield bruce.ashfi...@windriver.com wrote:
On 13-08-31 2:46 PM, Elvis Dowson wrote:
Hi,
In preparation for adding additional qemuarm machine configurations to
the linux-yocto kernels, can we rename the existing
standard/arm-versatile-926ejs branch
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
On Sun, 2013-09-01 at 09:20 -0500, Peter A. Bigot wrote:
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
On 13-09-01 8:32 AM, Peter A. Bigot wrote:
Thanks for the additional information. My entire expectation of how
linux-yocto metadata worked turns out to be wrong, but you've managed to
clear it up for me.
What I really wanted from linux-yocto was a way to isolate documented
kernel configuration
