The quick answer is yocto for everything or choose something else! If you just want to build the kernel why not build it on the parallella? There are posts about building the kernel on its own.. basically the process would be to get a working image with the matching kernel source, get the .config that was used to build the kernel from the environment then build the kernel source with that config and install that. Install that version of the kernel check it works then make your changes to the kernel driver source and rebuild. Have a look at
viewtopic.php?f=48&t=1230 to start with. The trick would be to start with a distribution that has the matching kernel source.
I moved to the ADI kernel because I needed the hdmi drivers for the ADI fpga modules and it seemed to be easiest to patch in the couple of files needed to get the epiphany driver going than struggle to back port ADI kernel stuff to an older kernel. Since then I have been extending the epiphany driver and am using the latest oh fpga and it all still works quite well. Dont forget that yocto also gives you a full gui interface if you want so you dont just have to stick with the command line!
The headless Parallella does have a working Vivado project.. its in a zip file on the parallella-hw see
https://github.com/parallella/parallell ... o/releases. What you have to do when mixing and matching is ensure that the get the correct matching epiphany sdk. That is what I try to present with my github parallella project.. the elink-redesign default branch uses the commit SRCREV = "be28d22caf3e09aa5813ec3a946279af2ee5191c" see
https://github.com/peteasa/meta-epiphan ... dk_1.0.inc that works with this zip file! So you would build your kernel then build that version of the epiphany-sdk, build your fpga project based on that zip file and it would all work and you could use the epiphany chip.
Ok so if you must just build the bits that you need with yocto.. this is how I do it: bitbake -c cleansstate virtual/kernel will clean the kernel, bitbake hdmi-image-debug will build everything but if its already been built it will just build the kernel and put it in the deploy folder. Same thing with the device tree and the bitstream so bitbake -c cleansstate parallella-hdmi-bitstream and bitbake -c cleansstate device-tree will do what you want. Now you want to fix up the kernel and the device tree with your own bits.. create an bbappend recipe and override the SRCREV and the SRC_URI and you can pull in your own local git bare repository with whatever you want (SRC_URI = "git:///home/peter/Projects/parallella/parallella-hw-peter.git") for example... Or you can patch the kernel on the go... bitbake -c cleansstate virtual/kernel will clean the kernel, bitbake -c configure virtual/kernel will pull in the kernel and patch it.. then you can add your own patches then bitbake hdmi-image-debug to build. It does not build the rootfs because it does not know that you have done some manual patching. Anyway by the time it starts doing the rootfs the bits you want are already in the deploy folder so you dont even have to wait if the rootfs is being built you can just pick what you need and copy to the sd card. I still think that the neatest solution would be to build the kernel and the device tree on the parallella for what you want to do.. but anything is possible!