Hi,Rini: Thanks for your reply!
Just use FDT as kernel parameter passed to linux kernel's entry
point?
That is one use, yes. But that may or may not be a recommended way to store the FDT for a platform (based on some discussion on the devicetrees mailing list, while there's no formal recommendations yet, having the shipped with platform FDT be done in such a way that it can be updated is strongly encouraged, possibly without having to replace the rest of the firmware as that's seen as a possible way to brick the hardware).
If you're planning on shipping hardware soon, with a device tree embedded within it, I would strongly encourage talking with devicetrees@vger.kernel.org about how to best do it, for your platform.
So, based on your experience: Do most ARM SOC production vendors adopt which way to store dtb binary?
I think storing dtb binary into a dedicated nv-storage(such as : some blocks in NAND chip) is a better way.
Best wishes,