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

[Philip Balister]

Also, have you considered the uenv.txt approach?

http://git.denx.de/?p=u-boot.git&a=search&h=HEAD&st=commit&s=uenv

Philip

On 08/06/2013 01:53 AM, Mike Looijmans wrote:
> On 08/05/2013 07:40 AM, Sipke Vriend wrote:
>>> 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.
> 
> Who will be doing so?
> 
> I've sent two kernel patches to Xilinx myself, and never got so much as
> a receipt confirmation. That wasn't very encouraging.
> 
>> 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
>>
> 
> I fail to see why this is better than "just insert an SD card and it
> will boot from it".
> 
>>> - 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
> 
> It is? How?
> 
> I experimented with Petalinux for a few days, but mostly the lack of any
> documentation and howto's made it -for me- harder to master than plain OE.
> 
> Mike.
> 
> 
> 
> Met vriendelijke groet / kind regards,
> 
> Mike Looijmans
> 
> 
> TOPIC Embedded Systems
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: (+31) – (0)499 - 33.69.79
> Telefax: (+31) - (0)499 - 33.69.70
> E-mail: mike.looijmans at topic.nl
> Website: www.topic.nl
> 
> Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn
> uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het
> e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking tot
> een derde instaan. Indien u als niet-geadresseerde dit bericht en de
> bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit
> bericht namens de geadresseerde te ontvangen, wordt u verzocht de
> afzender hierover direct te informeren en het e-mail bericht met de
> bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail
> bericht, waaronder de daarbij behorende bijlagen, door een ander dan de
> geadresseerde is onrechtmatig jegens ons dan wel de eventueel in het
> e-mail bericht of de bijlagen voorkomende andere personen. TOPIC
> Embedded Systems is niet aansprakelijk voor enigerlei schade
> voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht of
> de daarbij behorende bijlagen.
> 
> The contents of this message, as well as any enclosures, are addressed
> personally to, and thus solely intended for the addressee. They may
> contain information regarding a third party. A recipient who is neither
> the addressee, nor empowered to receive this message on behalf of the
> addressee, is kindly requested to immediately inform the sender of
> receipt, and to destroy the message and the enclosures. Any use of the
> contents of this message and/or the enclosures by any other person than
> the addressee or person who is empowered to receive this message, is
> illegal towards the sender and/or the aforementioned third party. TOPIC
> Embedded Systems is not  liable for any damage as a result of the use
> and/or acceptance of this message and as well as any enclosures.
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx