From: Dave H. <dhy...@gm...> - 2009-11-25 19:57:01
|
Hi Steven, On Wed, Nov 25, 2009 at 11:11 AM, Steven Kane <ste...@tp...> wrote: > Dave, > > I was able to get 'gpio-event' to compile for the Overo after applying > some tweaks to 'gpio-event-drv.c', 'gpio-event.bb' and Makefile. Attached > are these modified files. However, when I installed the package on the > Overo, I successfully added a pin to be monitored with the command: > 'gpio-event 144:r:20' as documented here: > http://docwiki.gumstix.org/GPIO_event, but 'gpio-event' did not show up in > '/dev' or '/proc'. Also, when I ran the command 'insmod gpio-event-drv.ko' I > got the error: 'insmod: error inserting 'gpio-event-drv.ko': -1 Invalid > module format'. Any ideas at this point? The first thing I would do, is to run the file command on the gpio-event-drv.ko file. I don't know if the file command is on the gumstix, but it's most likely on your build machine. Make sure that the .ko file was built for the ARM architecture. You should also be able to run modinfo (on your build machine for sure - maybe on the gumstix). I believe that there may also be some additional information logged in the /var/log/messages file. Typically, the problem with vermagic mismatch is caused because the version of toolchain/linux that the module was built for doesn't match the versions of the kernel running on the gumstix (i.e. your build environment is newer or older than the one used to build the image on your gumstix). -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |