On Monday 24 May 2010 17:26:48 Charles Manning wrote:
> Until we have a modules.dep with absolute paths, the modprobe won't work.
> Until that happens I guess I really don't have an easy way to transfer test
> scripts etc onto the board.
>
> I thought it would be easy to use sed  to massage the modules.dep  but for
> some reason the places I added them in the Makefile to didn't get called.
> Clearly I don't understand the make dependencies properly.
>
> Any hints on where to inject such sedness welcome.

I updated to r1115 but Wookey's fix didn't work for me. I have DEPMODVER of 
3.11.1 which the sed-based logic does not handle. I changed that to cut and 
it works for me.

With this I get loading modules :-) and setup is doing its thing as I write 
this...


Thanks to all, particularly  Wookey...


Here's a patch against r1115 that works for me:

Index: initrd/Makefile
===================================================================
--- initrd/Makefile	(revision 1115)
+++ initrd/Makefile	(working copy)
@@ -47,7 +47,7 @@
 	#fixup relative paths if depmod is newer than 3.4
 	#should check buildroot version too...
 	case $(DEPMODVER) in 3.*) \
-	    if expr `echo $(DEPMODVER) | sed -e"s/3.//;s/[-~].*$$//"` \> 4 ;then\
+	    if expr `echo $(DEPMODVER) | cut -d. -f2 ` \> 4 ;then\
 	      sed -i -e"s_kernel_/lib/modules/$(KERNVER)-pxa270/kernel_g" 
$(TARGETSKEL)/lib/modules/$(KERNVER)-pxa270/modules.dep ;\
 	    fi ;\
 	    ;; \