[meta-xilinx] what are the canonical xilinx mailing lists/repos these days?

[Sipke Vriend]

Hi Michael,

See inline.

>On Sunday, 4 August 2013 5:25 AM, Michael Rissi wrote:
>
>Dear all,
>Just hooking up on the topic: For the zedboard, I tried out the official 
>meta-xilinx layer, as well as meta-zynq-milo.
>Both worked great. meta-zynq-milo, however, has 2 main features I liked a 
>lot which are not in meta-xilinx:
>- One can easily change the device where the root filesystem is located by 
>changing the file autorun.scr. This allows to easily switch from rootfs over 
>nfs  to e.g. the rootfs on the second partition of the sd card. 

We investigated this and because this includes a significant u-boot 
patch, we suggest that the relevant content (if not all) should be RFC 
patched to git at xilinx.com (Cc meta-xilinx at yoctoproject.org). 
The u-boot-xlnx team can then comment.
If the patch (or derivative) is accepted, then we can cherry pick it 
into meta-xilinx - that will keep us in line with future u-boot-xlnx 
'zynq_common.h', rather than deviating.
Because u-boot is as flexible as it is, the meta-xilinx layer does not 
try to customise the default zynq_common.h as yet.

>For 
>meta-xilinx, this is much harder to change and needed quite some recipe 
>editing from my side. The default in meta-xilinx is a ram disk as rootfs, 
>limited to some 12MB.

Anyone wanting a large rootfs (and not able to use ramdisk) could use
tar.gz rootfs (built by default) and extract it to a second partition on 
sd card. The default U-boot configuration will fail on the missing
ramdisk: 
At this point the user can update&save the u-boot command to not load 
from ram and use the *-zynq7-mmcblk0p2.dtb file (currently only zedboard) 
to tell the kernel to use rootfs in second partition. If the settings are
saved in u-boot, this need only be done once.
See also related thread:
https://lists.yoctoproject.org/pipermail/meta-xilinx/2013-June/000138.html

>- A very nice feature is also the automatic creation of the BOOT.bin file 
>using the xilinx bootgen in meta-zynq-milo.
>

This kind of Xilinx tool integration and more is currently achieved by 
Xilinx's Petalinux. 
http://www.wiki.xilinx.com/PetaLinux

>Thus I wondered if there is any change that meta-zynq-milo and meta-xilinx 
>might be merged, or that at least some features from meta-zynq-milo are added 
>to meta-xilinx? 

Your request has been raised by others, and we understand it's reasoning, 
but we don't intend to add this in meta-xilinx as yet. 

> I am also willing to contribute and to test if needed.
>

One primary goal for meta-xilinx is to be the 'base layer' on which
other layers like meta-xilinx-community and meta-zynq-milo and say a layer 
controlled by you would sit. 
So, in the short term, rather than adding these features into meta-xilinx
you may consider creating a new layer which takes just the features you need
and layer on meta-xilinx. This would test our layer's layerability :-).

>Anyways, thanks a lot for your efforts, it's great to be able to use 
>openembedded to create images for the zynq!
>

You're welcome, it's good to see the layer being used and thanks for the 
feedback!
Sipke

>Best regards,
>Michael Rissi
>
>
>On Sat, Aug 3, 2013 at 2:05 PM, Elvis Dowson <elvis.dowson at gmail.com> wrote:
>Hi Robert,
>
>On Aug 3, 2013, at 3:06 PM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
>
>>  i can see the meta-xilinx layer that is now the official support
>> layer from xilinx (i'm assuming it's mirrored equally at both github
>> and yoctoproject.org, yes?). so, obviously, that's one layer i'll stay
>> on top of.
>>
>>  i see the new meta-xilinx-community layer, maintained by elvis
>> dowson and adrian alonso (which used to be "meta-xilinx"). is there
>> any official or unofficial relationship between the two layers?
>>
>>  and layers.openembedded.org still lists the layers meta-zynq and
>> meta-zynq-milo. so assuming i don't want to track 4 xilinx-related
>> layers, can i assume that i can focus on the official xilinx layer for
>> now? open to suggestions.
>You should use the meta-xilinx layer that is officially supported by
>Xilinx for the zedboard.
>
>The meta-xilinx-community layer is a layer for all the Xilinx legacy boards
>(e.g. the ones based on the Virtex-5, e.g. ML507) and other manufacturer
>boards based on Xilinx FPGAs. This layer was renamed to -community
>to avoid confusion as to which one was being officially supported by
>Xilinx.
>
>Best regards,
>
>Elvis Dowson
>_______________________________________________
>meta-xilinx mailing list
>meta-xilinx at yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-xilinx
>
>
>
>
>-- 
>**************************************************
>Michael Rissi, Ph.D.
>Product Development
>
>DECTRIS Ltd.
>Neuenhoferstr. 107
>5400 Baden
>Switzerland
>
>+41 56 500 2100 general
>+41 56 500 2101 fax
>+41 56 500 2125 direct
>michael.rissi at dectris.com
>www.dectris.com
>**************************************************
>
>
>Confidentiality Note
>This message is intended only for the use of the named recipient(s) 
>and may contain confidential and/or privileged information. If you are
>not the intended recipient, please contact the sender and delete the 
>message. Any unauthorized use of the information contained in this 
>message is prohibited.
>**************************************************
>