[meta-xilinx] few recipes-bsp questions

[Nathan Rossi]

On 19 February 2017 at 04:19, Richard Cagley <rcagley at gmail.com> wrote:
> 1.) Is there a preferred method for where to place ps7_init files?
> That is, as a patch to u-boot-xlnx or as an append via
> platform-init.bbappend?

It is up to you, but if you don't want to maintain patches then
platform-init with a bbappend is probably the way to go. Or you can
make your own recipe that "PROVIDES" the virtual/zynq7-platform-init
(which could fetch the ps7_init files from a source outside of your
layer). However since you are probably patching in support for your
board anyways (at least at the moment, maybe not in the future with
the changes to devicetree/kconfig) so it might be easier for you to
manage the adding of the ps7_init files there.

>
> 2.) Possibly similarly for device tree files. Patch or via
> recipes-bsp/device-tree? I see that microzed is in both places.

Generally speaking adding your device tree source as a bbappend to
device-tree is a great way to get started. But there is also
advantages to patching your device tree into the kernel. However it is
worth noting the device-tree recipe does actually pull the device tree
includes from the current selected kernel version, so there is no
major differences between building a device tree with the
'device-tree' recipe versus patching your device tree into the kernel.

So just for reference, meta-xilinx does not try to solve everyone's
use case. It is merely trying to provide a base that can be used to
get into things without having to create a full BSP from scratch. So
if you find that the way meta-xilinx solves a problem doesn't really
work for you, use the flexibility of OE to get things working the way
you need them to work.

Also with the microzed device tree, the reason it appears in the
kernel and in the device-tree files in the meta-xilinx layer is
because it was only recently added to the kernel, and so is only
available from newer kernel source (4.10 kernel specifically).

Sorry for taking so long to respond to your email.

Regards,
Nathan