From: Steve S. <sa...@gm...> - 2008-01-26 06:10:44
|
I discovered this evening that my recent check-in to enable the spi driver in the kernel broke the Marvell wifi driver: root@gumstix-custom-verdex:~$ modprobe wlan0 mcf25: Unknown symbol sbi_read_ioreg mcf25: Unknown symbol sbi_write_ioreg FATAL: Error inserting mcf25 (/lib/modules/2.6.21/extra/mcf25.ko): Unknown symbol in module, or unknown parameter (see dmesg) Backing out this change eliminates this error. Any theories? Until this is resolved I am backing out the SPI driver change. Note: this should not affect any of you who are doing user mode SPI programs like those that have been discussed on the list in recent days. Sorry if this inconvenienced anyone. Steve |
From: Dave H. <dhy...@gm...> - 2008-01-26 07:10:51
|
Hi Steve, On Jan 25, 2008 10:10 PM, Steve Sakoman <sa...@gm...> wrote: > I discovered this evening that my recent check-in to enable the spi > driver in the kernel broke the Marvell wifi driver: > > root@gumstix-custom-verdex:~$ modprobe wlan0 > mcf25: Unknown symbol sbi_read_ioreg > mcf25: Unknown symbol sbi_write_ioreg > FATAL: Error inserting mcf25 (/lib/modules/2.6.21/extra/mcf25.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > > Backing out this change eliminates this error. > > Any theories? Looking at the src_cf8385/Makefile, it makes the rather presumptuous decision that if CONFIG_SPI is defined then you'll be using SPI to talk to the WLAN module (and hence tries to call sbi_read_ioreg). You can see that -DSPI is passed in the Makefile if CONFIG_SPI gets defined. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Steve S. <sa...@gm...> - 2008-01-26 07:29:52
|
Thanks Dave! I'll re-enable the SPI module after I figure out whether I want to deal with the case when we actually *do* want to connect SPI to the module now or later. I think it will be a rare enough occurrence that I'll probably deal with it later :-) Steve On Jan 25, 2008 11:10 PM, Dave Hylands <dhy...@gm...> wrote: > Hi Steve, > > On Jan 25, 2008 10:10 PM, Steve Sakoman <sa...@gm...> wrote: > > I discovered this evening that my recent check-in to enable the spi > > driver in the kernel broke the Marvell wifi driver: > > > > root@gumstix-custom-verdex:~$ modprobe wlan0 > > mcf25: Unknown symbol sbi_read_ioreg > > mcf25: Unknown symbol sbi_write_ioreg > > FATAL: Error inserting mcf25 (/lib/modules/2.6.21/extra/mcf25.ko): > > Unknown symbol in module, or unknown parameter (see dmesg) > > > > Backing out this change eliminates this error. > > > > Any theories? > > Looking at the src_cf8385/Makefile, it makes the rather presumptuous > decision that if CONFIG_SPI is defined then you'll be using SPI to > talk to the WLAN module (and hence tries to call sbi_read_ioreg). You > can see that -DSPI is passed in the Makefile if CONFIG_SPI gets > defined. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |