Hi, sorry also from my side for the delay.. I guess, bringing Altera/Intel DTS to the kernel is getting a longer story. But I even can see light now. I keep you guys up-to-date, if any news.
On Sun, Oct 27, 2024 at 5:09 PM Marek Vasut <[email protected]> wrote: > > On 10/23/24 10:10 PM, Lothar Rubusch wrote: > > Hi, > > sorry for the late reply. > > >>>> Can this be generated using binman instead ? > >>> > >>> This would a oportunity for me to learn the binman tool. Great idea! I > >>> need to read a bit more on binman to get a better understanding. I'll > >>> give it a try and let you know. Thank you. > >> > >> This commit might help: > >> > >> 5fccc2891e28 ("ARM: dts: stm32: Generate u-boot.itb using binman on DH > >> STM32 DHSOM") > >> > > > > I face a problem here. First, to apply binman stances in the .dtsi and > > integrating it as -u-boot.dtsi is very interesting and I actually like > > the solution to bind everything togerther in this way. > > > > But, I face the situation where the very design specific bitstream(s) > > for the FPGA are actually not supposed to be upstreamed. Having u-boot > > binaries and bitstream as .itb separate, allows to build the u-boot > > part even w/o the bitstream, i.e. the u-boot setup can be quite > > generic, can be tested and verified building. Is this still possible > > if binman requires it as binary blob? > > I believe so, U-Boot CI does use binman to build e.g. imx8m targets > which do require extra firmware, but during the CI build that extra > firmware is replaced by blank empty files by binman. It does print some > sort of warning that the files are missing ... try e.g. 'make > imx8mp_dhcom_pdk3_defconfig ; make' and you should see the behavior > locally too. > I totally got the u-boot log wrong. The build runs through with or without blobs. So, there is no open issue from my side. If I build w/o blobs, I see the warning in red - it's actually just a warning and not an error as I initially thought. So, the current setup as is, actually builds on binman. It is ready when you are. I'm issuing a version 5 now, just for having the document/typo fixes excluded, as Simon asked. Best, L
