>>> well no, this isn't the right way to do this. quirks need to be based on >>> real hardware information (e.g. DMI) and not a driver name. >> >> Thanks for the review. Could I use dmi_match function inside is_byt_cr? > > > Yes, however it's the first time I see a quirk based on DMI_CHASSIS_VERSION. > we use PRODUCT or BOARD usually. Not a problem. I can change it. I have these info available from dmi: bios_date: 08/01/2014 bios_vendor: LENOVO bios_version: 01WT17WW board_asset_tag: NO Asset Tag board_name: INVALID board_serial: HA07YER9 board_vendor: LENOVO board_version: SDK9A6N2HVWIN chassis_asset_tag: NO Asset Tag chassis_serial: HA07YER9 chassis_type: 11 chassis_vendor: LENOVO chassis_version: 1051F modalias: dmi:bvnLENOVO:bvr01WT17WW:bd08/01/2014:svnLENOVO:pn60073:pvr1051F:rvnLENOVO:rnINVALID:rvrSDK9A6N2HVWIN:cvnLENOVO:ct11:cvr1051F: product_name: 60073 product_serial: HA07YER9 product_uuid: 39FFE49E-1918-884A-9499-CC7705A289C9 product_version: 1051F sys_vendor: LENOVO uevent: MODALIAS=dmi:bvnLENOVO:bvr01WT17WW:bd08/01/2014:svnLENOVO:pn60073:pvr1051F:rvnLENOVO:rnINVALID:rvrSDK9A6N2HVWIN:cvnLENOVO:ct11:cvr1051F: _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
