Hi Lucien, Hi Marek, On Fri, Apr 18, 2025 at 11:57:19PM +0800, Lucien.Jheng wrote: > Hi Marek Vasut > > Thanks for the review. > > The next commit will change the loading of the PHY firmware to the > filesystem on a block device.
Please keep in mind that most systems using this PHY are (like the OpenWrt One, for example) simple embedded devices with only a small amount of NAND or NOR flash. Loading the firmware from a filesystem means overhead and complexity, while loading it from a simple MTD partition, raw UBI volume or one of the EMMC boot hw partitions is a better match to the reality of the devices it is being used on, making the process less complex and more deterministic, and hence more robust. > [...] > Marek Vasut 於 2025/4/6 下午 09:30 寫道: > > [...] > > > > Can this do the same thing as Aquatia PHY and load the PHY firmware from > > filesystem on block device instead , using the blk* or fs* commands ? > > Then the hard-coded filesize and co. won't be necessary. Note that the size is afaik given by the hardware in this case, it won't every change. Hence any handling of a more dynamic approach of loading the firmware will also have to come with a size-check against the (again) hard-coded size anyway. > > > > If you need board specific loading override, implement __weak default > > loading from file on filesystem by default (see what Aquatia does) and > > then override the loading function on board or architecture level. That can work, but in practice it will lead to code duplication, as all platforms using those PHYs are kinda similar (ie. MT7981, MT7986 and probably Airoha/EcoNet router SoCs as well) > > > > U-Boot really needs a proper generic firmware loader, because this > > firmware stuff keeps showing up more and more, but I cannot ask you to > > write one only because of this PHY ... but if you are up for a challenge > > ... > > > > [...]
