[meta-xilinx] Bitstream/Boot.bin/etc - Providers/Virtual targets

[Michal Simek]

Hi Andrey,

On 02/13/2014 05:47 PM, andrey wrote:
> Michal,
> 
> I  admit that my ezynq code has some flaws (it is my first program in Python), but I'm sure it can do the job,
 especially with the help of others (we had access to only 3 boards - Microzed, our camera and  Xilinx ZC706).

Yes, I know and I really appreciate it and as we discussed I have no problem with it. What I really didn't like
was that the part of that is building and there is strong dependency on specific version.
I believe you will agree with me is that this discussion is currently just about low level board setup
and your tool is wonderful for that.
I do use ps7_init.c files because it is just easy for me and if you are able to generate this file
in different way then it is great.
That's why I am suggesting you to change ezynq to just generate ps7_init.c file or more files but
with one top level function ps7_init() which just run this configuration in proper place.

I know that you are using full u-boot instead of u-boot SPL and we can definitely discuss this
how to fix it if you still want to use full u-boot running from SPL.


Usually in my work I prefer GUI tools - as I wrote you earlier I'm now working on a replacement to Vivado GUI
with Eclipse-based software more convenient for myself (and I hope to some other developers too). But in the case
of bootloader generation I do not see much advantage of fancier GUI - all the commercial boards (like Zedboard)
can come with ready to use include files, and for hardware developers (as myself) it is not a big hassle to go
through every single line of the hardware-specific configuration and make sure is what I need for the new design.
 This is an extra pre-flight test that can save from costly re-spins of the new boards.

Definitely.

> 
> As for incompatibility of GPLv3+ we used with U-Boot GPLv2 - I understand that U-Boot needs the same license as Linux kernel, 
so we probably can re-license it under that older version.

If we are talking about boot.bin generation script then GPLv3 is not a problem and I have checked this
with Wolfgang Denk. If your generated files have GPLv3 license that it is the problem because GPLv3
is not compatible with GPLv2 (At least that was my take away from that discussion with WD).

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20140214/44640be5/attachment.pgp>