Guennadi Liakhovetski wrote:

On Fri, 23 Jan 2009, Valentin Longchamp wrote:

quoted

So the devices are registered fine. My problem is that the driver is not
registered for me: This should be done by the subsys_initcall but
ipu_init is never called.

Are you sure you have CONFIG_MX3_IPU=y?... sorry, I don't see any other 
possibility why a subsys_initcall() would not be called. You can also 
check if it's being compiled and linked, and if you do

arm-linux-objdump -Dr vmlinux |grep ipu_init

you should see something like

c0014c94 <ipu_init>:
c0014c94:       e1a0c00d        mov     ip, sp
--
c0019c70 <__initcall_ipu_init4>:
c0019c70:       c0014c94        mulgt   r1, r4, ip

Well I have all of them ... Taht's why I really don't understand what's
going on.

However I don't have the same asm instruction for the initcall:

c00192b4 <__initcall_ipu_init4>:
c00192b4:       c00141e8        .word   0xc00141e8

But that's the address of my ipu_init
c00141e8 <ipu_init>:
c00141e8:       e1a0c00d        mov     ip, sp
c00141ec:       e92dd800        push    {fp, ip, lr, pc}
c00141f0:       e24cb004        sub     fp, ip, #4      ; 0x4

I think something is working badly with the initcall (subsys). Has
someone already experienced something similar ?

Thanks

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword