On Tue, Oct 01, 2019 at 06:14:23PM +0000, Mario.Limonciello@xxxxxxxx wrote: > One more thought; would you consider exporting to sysfs sw->config.vendor_id? > Maybe an attribute that is switch_vendor? > > Userland fwupd also does validation on the NVM and will need to follow this. > The same check will go into fwupd to match the vendor and lack of nvm_non_active0 > to mark the device as not updatable. When the checks in the kernel get relaxed, > some NVM parsing will have to make it over to fwupd too to relax the check at that point. The original idea was that the kernel does the basic validation and userspace then does more complex checks. Currently you can compare the two NVM images (active one and the new) and find that information there. I think fwupd is doing just that already. Is that not enough?
