Hi Marcel, > it is also way harder to use and things need to be manually configured. Don't know know when the > device needs calibration information or not. And you can just request_firmware() that file. If it is > there, then load it, if not then skip the step. Thanks for your suggestion. This approach should work for me. > > > The firmware_request() requires a relative file path under /lib/firmware/. > > What is the standard location you are referring to? > > You have to create proper filenames for your hardware. Like mrvl/cal_data_v1.conf or similar. Sure. > As I said above, the device should know if it needs calibration or not. And just installing a file on > disk is simpler than having to modify the module parameters somewhere. This makes sense. I'll take your approach and re-spin the patch. Thanks, Bing -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
