On Tue, Nov 3, 2015 at 3:54 AM, Anders Darander wrote:
> * Andre McCurdy [151103 11:34]:
>
>> On Mon, Nov 2, 2015 at 11:05 PM, Anders Darander
>> wrote:
>> > * Andre McCurdy [151102 20:35]:
>
>> >> See the "IMAGE_TYPES" variable for a list of rootfs types which are
>> >> supported. There's sup
--
Andrei Gherzan
On Tue, Nov 3, 2015 at 5:47 AM, Raj Jar wrote:
> I got this error when i do bitbake rpi-hwup-image
> I suspect error come from mcopy .
> how to recover this error
> MACHINE ?="raspberry pi"
>
>
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing Ru
Dear all,
I'm having a machine A and a machine B.
This two machines are built against the same image class and in the same
build folder.
But on machine A there is a recipe LAMBDA which is not include in
machine B.
The package LAMBDA is shared in the same folder
cortexa9hf_vfp_neon(Machi
I'm quite new to yocto so still have a lot to learn. I'm trying to
include the DMA drivers in my yocto build for a Zynq based on the
meta-xilinx layer (http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/).
I thought I'd be able to add them in the kernel configuration
(menuconfig) by running (fr
On 11/04/2015 08:35 AM, Toby Gomersall wrote:
> I'm quite new to yocto so still have a lot to learn. I'm trying to
> include the DMA drivers in my yocto build for a Zynq based on the
> meta-xilinx layer (http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/).
You should try emailing this list for
Hi,
We've tried building the linux-xlnx tree standalone and we have the DMA
drivers available to add in menuconfig but not when I build
core-image-minimal. I thought the full build would pick up the
linux-xlnx kernel and make the same options available. Is there
something I need to do to make them
On Thu, Nov 5, 2015 at 12:20 AM, Toby Gomersall
wrote:
> Hi,
>
> We've tried building the linux-xlnx tree standalone and we have the DMA
> drivers available to add in menuconfig but not when I build
> core-image-minimal. I thought the full build would pick up the
> linux-xlnx kernel and make the s
On 11/3/15 5:44 AM, Manjeet Pawar wrote:
>> This patch needs to be applied to 'cross_prelink_aarch64' branch.
>> It fixes tls1, tls2, tls4, tls5, tls6 test cases of prelink testsuite.
>> tls3 gets failed but this test case fails without prelink as well on AARCH64
>
>I'm still getting segfaults here
Hi Toby,
Please compare with http://www.wiki.xilinx.com/Linux+Drivers. Most of the DMA
drivers aren't mainlined by now. You need to add them by yourself currently.
Regards,
Martin
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf
There are probably a number of things wrong including some configuration errors
I’ve made being that
I’m just getting started. My ultimate goal is to cross-compile tools to
augment the OS running on a
3DR Solo drone, here’s the doc on linux binary builds as you can see it’s
minimal, but I’ve re
Hi,
I was trying to "patch a patch" in a u-boot recipe using standard
bbappends technique. I added a task before do_patch after do_unpack
to munge the patch that was broken. Here is what seems to happen:
do_unpack:
copies all the patch files from the metadata layer into ${WORKDIR}
do_fix_p
On 11/04/2015 01:08 PM, Jeff Waller wrote:
> There are probably a number of things wrong including some configuration
> errors I’ve made being that
> I’m just getting started. My ultimate goal is to cross-compile tools to
> augment the OS running on a
> 3DR Solo drone, here’s the doc on linux bi
Remove several people who no longer should be considered owners of recipes,
reassign more to the new distro team, add new recipes and prune removed ones.
Signed-off-by: Ross Burton
---
meta-yocto/conf/distro/include/maintainers.inc | 701 +
1 file changed, 352 insertions(
> On Nov 4, 2015, at 11:57 AM, Chris Hallinan wrote:
>
> Hi,
>
> I was trying to "patch a patch" in a u-boot recipe using standard
> bbappends technique. I added a task before do_patch after do_unpack
> to munge the patch that was broken. Here is what seems to happen:
>
> do_unpack:
>cop
Hi All,
I have just noticed that if I execute
bitbake u-boot -c clean
and then
bitbake fsl-image-x11
The u-boot file in tmp/deploy/images// gets updated, but the .sdcard
image file does not get updated.
How can I generate the new .sdcard image file that contains the new u-boo
> On Nov 4, 2015, at 7:32 PM, Roberto wrote:
>
> Hi All,
>
> I have just noticed that if I execute
> bitbake u-boot –c clean
>
> and then
> bitbake fsl-image-x11
>
> The u-boot file in tmp/deploy/images// gets updated, but the .sdcard
> image file does not get updated.
>
> How can I gen
16 matches
Mail list logo
