On Thu, Oct 22, 2009 at 11:38 PM, Wolfgang Grandegger <[email protected]> wrote: > christian pellegrin wrote: >> On Thu, Oct 22, 2009 at 11:32 PM, Paul Thomas <[email protected]> wrote: >> >>> the first it describes the two sections that need to go in the board & >>> devices file. However when I add those sections as would be expected I >>> can't compile the regular uImage because of the non-existent >>> references. If I add LINUXINCLUDE=socket-can_kernel_path, then I get >>> kernel/bounds.c errors. >> >> Hi, well it will be solved when the drivers goes mainline. I'm trying >> to do that but unfortunately I can work on it only on my free time, so >> it will take a couple of days. A quick fix is just copy the file >> mcp251x.h somewhere in the include directories of the kernel. Don't >> mix include files from the SVN and the code from mainline. It could >> give you surprising results in general (perhaps it's ok for socketcan >> but I'm not sure). > > You can create proper files for the kernel from the SVN trunk using the > script strip-src. > > $ cd trunk > $ ./strip-src -m -i -v 2.6.31 \ > kernel/2.6/include/socketcan/can/platform/mcp251x.h \ > > $KERNELDIR/include/linux/can/platform > $ ./strip-src -m -i -v 2.6.31 \ > kernel/2.6/drivers/net/can/mcp251x.c \ > > $KERNELDIR/drivers/net/can > > Furthermore, you need to update the Kconfig and Makefile as well, but > that trivial. > > Wolfgang. >
Thanks for the responses. If I include the .h that fixes some of it. But in mcp251x_info there is still .board_specific_setup = &mcp251x_setup. mcp251x_setup is in the .c file, but if I include the .c file it's missing more of the can stuff. is there a way to define a prototype for mcp251x_setup, that then gets set correctly when the module is loaded in? thanks, Paul _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
