[meta-xilinx] Bitstream/Boot.bin/etc - Providers/Virtual targets
Philip Balister
philip at balister.org
Thu Feb 13 05:30:14 PST 2014
On 02/13/2014 07:05 AM, Michal Simek wrote:
> Hi guys,
>
> nice discussing and maybe good time to jump into.
>
> On 02/13/2014 08:15 AM, Cjw X wrote:
>> We should unequivocally throw the FSBL into the fires of Mount Doom.
>>
>> I've been working with u-boot-spl running on my microzed for about a month
>> now, and I'm already considerably happier with it.
>
> spl is nice and it will be supported in mainline u-boot soon.
> My patches have been already reviewed and waiting for adding to arm custodian
> tree.
> It means u-boot spl will be available for everybody.
>
>> The spl design is derived from ezynq from elphel, so it should be pretty
>> extensible to different platforms. I'll have a zedboard to play with next
>> week, so I'll get it up and running then.
>
> Andrey has done great work on this but how this all fit together
> is not the best. That's why currently I have used ps7_init files
> instead of ezynq project.
> I was discussing this with Andrey and meybe in future Andrey will
> change ezynq just for lowlevel setup generation because this is
> that difference.
Having a tool to generate the ps7_init* files outside of xps/ise/vivado
will be really helpful. The SPL support goes a long way to making it
easier to do complete system builds without dependencies on Xilinx tools.
For meta-xilinx, I'd like to see the u-boot recipe become SPL aware and
build spl if the ps7_init* files are available at build time. This is on
my todo list.
Philip
>
>> I've considered trying to get u-boot to generate an spl build from the
>> ps_init code that xilinx spits out of the sdk. It is nice on some level,
>> but somewhat contrary to my end goal. My goal is to completely divorce Zynq
>> software development from Xilinx
>
> Not everybody is able to generate by hand configuration for their design.
> Not everybody wants to do it by hand when they have to do the same in design tools.
> Using projects like ezynq for generation is nice and definitely it is nice
> to see it but I don't believe that anybody will be able to invest time
> to maintain this in long term.
>
> As I told to Andrey will be good to change ezynq just to generate private
> ps7_init.c file because it is that thing you are asking for.
>
> I am not quite sure what you mean by "My goal is to completely divorce Zynq
> software development from Xilinx" but feel free to start writing all drivers/
> support for zynq from scratch without any xilinx help. None can stop you
> to do so.
>
>> Next on my list is some updates to the kernel
>> 1) Fix the mmc writing bug (probably a hack because I think it is a
>> hardware flaw, but I haven't looked into it)
>
> If you mean dma allocation below kernel start address then fix is on way
> to mainline kernel.
>
>> 2) Fix the xdevcfg driver to be a misc driver so that udev recognizes it
>> properly
>
> there will be much more changes than just this.
>
> Thanks,
> Michal
>
>
>
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20140213/c4edcf2b/attachment.pgp>
More information about the meta-xilinx
mailing list