To test this, you'll need a firmware image for your module. It must be in hcd format. Name it as /lib/firmware/fw-VVVV_PPPP.hcd where VVVV and PPPP are the module's VID and PID, for example /lib/firmware/fw-0a5c_21e3.hcd for module 0a5c:21e3.
If you don't have a hcd firmware, please try to get a hex firmware from windows driver, and convert it into hcd format.
You can find the tool at https://github.com/jessesung/hex2hcd .
$ git clone git://github.com/jessesung/hex2hcd.git
$ cd hex2hcd
$ make
$ hex2hcd <input_file>.hex fw-xxxx_yyyy.hcd
Hi Christophe,
To test this, you'll need a firmware image for your module. It must be in hcd format. Name it as /lib/firmware/ fw-VVVV_ PPPP.hcd where VVVV and PPPP are the module's VID and PID, for example /lib/firmware/ fw-0a5c_ 21e3.hcd for module 0a5c:21e3.
If you don't have a hcd firmware, please try to get a hex firmware from windows driver, and convert it into hcd format. /github. com/jessesung/ hex2hcd .
You can find the tool at https:/
$ git clone git://github. com/jessesung/ hex2hcd. git
$ cd hex2hcd
$ make
$ hex2hcd <input_file>.hex fw-xxxx_yyyy.hcd