On 6/19/24 18:21, Jakub Kicinski wrote: > [Some people who received this message don't often get email from kuba@xxxxxxxxxx. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] > > On Wed, 19 Jun 2024 07:16:20 +0000 Omer Shpigelman wrote: >>>> Are you referring to get_module_eeprom_by_page()? if so, then it is not >>>> supported by our FW, we read the entire data on device load. >>>> However, I can hide that behind the new API and return only the >>>> requested page if that's the intention. >>> >>> Well, if your firmware is so limited, then you might as well stick to >>> the old API, and let the core do the conversion to the legacy >>> code. But i'm surprised you don't allow access to the temperature >>> sensors, received signal strength, voltages etc, which could be >>> exported via HWMON. >> >> I'll stick to the old API. >> Regaring the sensors, our compute driver (under accel/habanalabs) exports >> them via HWMON. > > You support 400G, you really need to give the user the ability > to access higher pages. Actually the 200G and 400G modes in the ethtool code should be removed from this patch set. They are not relevant for Gaudi2. I'll fix it in the next version.
