Hi Daniel, > If CONFIG_FW_LOADER is not set, the speedtouch driver causes kernel > compilation/linking to fail: > > LD .tmp_vmlinux1 > drivers/built-in.o(.text+0xcb9b7): In function `speedtch_find_firmware': > : undefined reference to `request_firmware' > drivers/built-in.o(.text+0xcba30): In function `speedtch_find_firmware': > : undefined reference to `request_firmware' > drivers/built-in.o(.text+0xcba64): In function `speedtch_find_firmware': > : undefined reference to `request_firmware' > drivers/built-in.o(.text+0xcbb31): In function `speedtch_load_firmware': > : undefined reference to `release_firmware' > drivers/built-in.o(.text+0xcbb57): In function `speedtch_load_firmware': > : undefined reference to `release_firmware' > > How should this be dealt with? Should FW_LOADER be depended on/selected by > speedtouch? > Or can we safely use the USE_FW_LOADER define to exclude the firmware stuff? > (See the drivers/usb/atm/speedtch.c file - the USE_FW_LOADER define is used > to > avoid compiling some firmware-related parts of the code already).
in particular USE_FW_LOADER is used to avoid compiling speedtch_find_firmware and speedtch_load_firmware, so the errors you're seeing means that USE_FW_LOADER is defined. It is defined as follows: #if defined(CONFIG_FW_LOADER) || defined(CONFIG_FW_LOADER_MODULE) # define USE_FW_LOADER #endif So... is CONFIG_FW_LOADER or CONFIG_FW_LOADER_MODULE set in your .config? Thanks, Duncan. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
