Here are two machines I've tried this one where I receive the above
warnings:
https://github.com/kratsg/meta-l1calo/blob/bumpToRocko/conf/machine/gfex-prototype3a.conf
https://github.com/kratsg/meta-l1calo/blob/bumpToRocko/conf/machine/gfex-prototype4.conf
Both of these include my tune-gfex-zyn
Hi Manju,
Just running something like bitbake zynq-base which is just an image
inheriting from core-image plus 2 other python packages I've written (added
as an install).
I'm still running into lots of issues with my images with the change to
rocko, so I'm not sure where I'm going wrong...
G
On
> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Giordon Stark
> Sent: Sunday, March 18, 2018 10:20 AM
> To: meta-xilinx@yoctoproject.org
> Subject: [meta-xilinx] wic creation manifest warnings with zynqmp-pmu
Hi,
I'm switching over to rocko, trying to get my images to compile again, and
I see these warnings?
WARNING: zynq-base-1.0-r0 do_image_wic: Manifest
/local/d4/gstark/poky/build/tmp/sstate-control/manifest-x86_64_aarch64-zynqmp-pmu-gcc-cross-microblazeel.populate_sysroot
not found?
WARNING: zynq-
Hi Nathan,
> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Nathan Rossi
> Sent: Sunday, March 18, 2018 6:33 AM
> To: Alejandro Enedino Hernandez Samaniego
> Cc: meta-xilinx@yoctoproject.org
> Subject: Re: [met
Hi,
We are in process and we should have all layers in layer-index. There is a new
requirement to run yocto-check-layer before adding it to layer-index, we are in
the process and will get it updated upstream
Thanks,
Manju
From: Giordon Stark [mailto:kra...@gmail.com]
Sent: Sunday, March 18, 20
Hi Nathan,
On Sun, Mar 18, 2018 at 6:29 AM Nathan Rossi wrote:
> On 18 March 2018 at 04:57, Giordon Stark wrote:
> > Hi,
> >
> > Based on Jorge's suggestion (cc'd), I uncommented my lines in
> > device-tree.bbappend to set compatible machine = ".*" for my particular
> > boards as it is being do
I see, so does meta-xilinx-contrib get added to this layer indexing too,
since it is a layer? I don't see it, hence my confusion.
G
On Sun, Mar 18, 2018 at 6:29 AM Nathan Rossi wrote:
> On 18 March 2018 at 03:40, Giordon Stark wrote:
> > Hi,
> >
> > Since the meta-xilinx "layer" is really meta
On 8 March 2018 at 11:15, Alejandro Enedino Hernandez Samaniego
wrote:
> oe-core has upgraded binutils to v2.30, which caused some of our
> patches to fail, rebase these along with other minimal changes to
> avoid these errors and provide compatibility with latest oe-core.
Unfortunately your mail
On 18 March 2018 at 03:40, Giordon Stark wrote:
> Hi,
>
> Since the meta-xilinx "layer" is really meta-xilinx-bsp and
The root of the meta-xilinx git repository is not actually a layer. So
it doesn't have an entry in the layer index.
> meta-xilinx-contrib -- shouldn't this page
> (http://layers.
On 18 March 2018 at 04:57, Giordon Stark wrote:
> Hi,
>
> Based on Jorge's suggestion (cc'd), I uncommented my lines in
> device-tree.bbappend to set compatible machine = ".*" for my particular
> boards as it is being done upstream... and bitbake seems to be happier with
> that, but then I run int
11 matches
Mail list logo