Hello Antony, On 11.08.2018 12:55, Antony AbeePrakash X V wrote: > Coreboot FSP Performance Data > ID: 950 - 951: 8118676370 - 2354813461 --> 4433ms (TS_FSP_MEMORY_INIT_START > - TS_FSP_MEMORY_INIT_END) > ID: 952 - 953: 10675414728 - 8905813067 --> 1361ms > (TS_FSP_TEMP_RAM_EXIT_START - TS_FSP_TEMP_RAM_EXIT_END) > ID: 954 - 955: 11761158519 - 10934089420 --> 636ms > (TS_FSP_SILICON_INIT_START - TS_FSP_SILICON_INIT_END) > ID: 956 - 957: 19265617974 - 19265559282 --> 0ms > (TS_FSP_BEFORE_ENUMERATE - TS_FSP_AFTER_ENUMERATE)
given that Google uses the same SoC for Chromebooks, I would expect about ten times faster numbers. What FSP binary do you use? There is one in Intel's FSP GitHub repo[1]. Maybe try that one if you haven't already. I know there are also bina- ries with additional debugging enabled; that might slow things down. > > Can we reduce the above mentioned time taken by modifying the FSP source ? > Please advice. Questions about the FSP source are better directed towards Intel. They do not want this community to know the source. Nico [1] https://github.com/IntelFsp/FSP/tree/ApolloLake -- coreboot mailing list: [email protected] https://mail.coreboot.org/mailman/listinfo/coreboot
