[meta-xilinx] Today's work

[Sipke Vriend]

Hi Philip,

>
>
>-----Original Message-----
>From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-bounces at yoctoproject.org] On Behalf Of Philip Balister
>Sent: Friday, 6 September 2013 5:58 AM
>To: meta-xilinx at yoctoproject.org
>Subject: [meta-xilinx] Today's work
>
>First, this should be non-controversial:
>
>https://github.com/balister/meta-xilinx/commits/3.10-fix
>
>Without this, the recipe builds the wrong version. I noticed when I had
>trouble applying patches for my custom hw via a bbappend kernel.
>

Linux-xlnx 3.10 recipe is a place holder for when linux-xlnx.git 
master-next work goes to master branch.
Until then, anyone not using the preferred version 3.8, as selected in 
machine files, should use linux-xlnx-dev target as it selects master-next 
branch, which is currently 3.10.

>And the ever popular, build a BOOT.BIN file as part of the u-boot recipe.
>
>https://github.com/balister/meta-xilinx/commits/boot-bin-2
>
>This works for me very well. Included is an example the builds BOOT.BIN
>for the zedboard, and I can confirm you can use a bbappend in another
>layer to support custom hardware. If your machine does not have the
>fsbl.ekf file, or your build machine does not have bootgen in the path,
>the u-boot build completes and does not attempt to create the BOOT.BIN file.
>
>I'd love to see this upstream so I can kill off this branch.
>

There is no plan currently to add boot.bin functionality into meta-xilinx.
As previously discussed please consider creating a layer over meta-xilinx 
to hold this boot.bin functionality, or discuss with Elvis if this would 
be appropriate for meta-xilinx-community.

Regards
Sipke

>Philip
>_______________________________________________
>meta-xilinx mailing list
>meta-xilinx at yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-xilinx
>
>