On 09/06/2017 07:06 AM, Chee, Tien Fong wrote: [...] >>>>> The BSP tool is used to describe internal FPGA in SOCFPGA. >>>>> Other >>>>> external FPGAs other than SOCFPGA itself, it can be programmed >>>>> through >>>>> U-boot. >>>> The BSP tool is broken if it generates broken DT, do I have to >>>> repeat >>>> myself ? >>>> >>> BSP tool is only generate the RBF filename for FPGA inside SOCFPGA. >>> Multiple external FPGA are configured through U-boot. >> What happens if you have FPGA connector over SPI ? >> > I assume you are saying FPGA connected to EPCQ
No, I mean FPGA connected over SPI bus. >, and this is one of the > external FPGA configuration, like PCIE. For any external FPGA > configuration, FPGA itself/external HOST would get the FPGA data from > storage such as EPCQ and configuring the FPGA without HPS/Bootloader > intervine. SPL/U-boot would skip the FPGA configuration process when > they see the mode is set to external FPGA configuration. > > I know you want a DT to describe all FPGAs with FPGA node and their own > data filename in every node. But, at this moment, all external FPGAs > chip other than SOCFPGA itself are configured through U-boot(script & > env variable), or external FPGA configuration method. I want DT which describes hardware and is not misdesigned crap. Just because the BSP tool is broken does not mean I can allow upstream to accept that, no way. > How about i just create a FPGA node for SOCFPGA, with FPGA data > filename within the node? Isn't that what the FPGA manager in mainline Linux does already ? -- Best regards, Marek Vasut _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot