> There's been multiple rounds of discussions with Curtis, we introduced > DMI_OEM_STRING but it's still not good enough, and now the previous > conventions are not being followed on what is a relatively old platform > already... Thanks for pointing that out. ChromeOS uses the fw_path module parameter for JSL boards so I missed this. The DMI_BIOS_VERSION should be consistent across all Chromebooks assuming 3rd party firmware wasn't installed. I'll throw up another patch addressing this.
