On 03/21/16 01:54, Ian Lepore wrote: > On Sun, 2016-03-20 at 23:40 +0100, Jilles Tjoelker wrote: >> On Sun, Mar 20, 2016 at 04:05:34PM -0600, Ian Lepore wrote: >>> On Sun, 2016-03-20 at 22:33 +0100, Guido Falsi wrote: >>>> the full error in dmesg is the same as stated before: >> >>>> link_elf_obj: symbol mmc_driver undefined >>>> linker_load_file: Unsupported file type >> >>>> Meybe the symbol is optimized out by the compiler in the module? >> >>> I suspect this is caused by my r292180 back in December. I'm >>> trying to >>> figure out if that's the case and if so, how to fix it. >> >> I think this is caused by the missing MODULE_DEPEND. The kernel >> linker >> only looks for symbols in the ELF objects containing the module >> itself >> and its declared dependencies. >> >> If mmc is compiled into the main kernel image, this is always >> satisfied. >> > > Thanks for the clue about the linker, it would have taken me forever to > figure that out by flailing around like I was doing. > > Hopefully this is all fixed now with r297127, but I was only able to > test it on arm systems (I have no x86 with sdhci). > Sorry for the delay, I updated the machine to r297146 and can confirm the problem is gone. Thanks you a lot for the quick fix! -- Guido Falsi <mad_at_madpilot.net>Received on Tue Mar 22 2016 - 12:23:43 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:03 UTC