Guennadi Liakhovetski wrote:

On Fri, 23 Jan 2009, Valentin Longchamp wrote:

quoted

quoted

root@mx31moboard:~# ls -al /sys/bus/platform/drivers
drwxr-xr-x    6 root     root            0 Oct 16 13:50 .
drwxr-xr-x    4 root     root            0 Jan  1  1970 ..
drwxr-xr-x    2 root     root            0 Jan  1  1970 generic-bl
drwxr-xr-x    2 root     root            0 Jan  1  1970 imx-uart
drwxr-xr-x    2 root     root            0 Oct 16 14:05 mx3_sdc_fb
drwxr-xr-x    2 root     root            0 Jan  1  1970 physmap-flash

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

Ok let's get back to this point. The initcall_debug=1 boot option helped
a lot (thanks Russel). So all initcalls correctly are called ipu_init
inclusive (my pr_debug calls did show nothing even with the debug and
dynamic_printk option, so I thought initcalls were not called ... I
don't understand what happened here). But the toolchain is not the
problem, and nor the initcalls.

So I know that ipu_init fails with -ENODEV and I am investigating. Sorry
for all the mails and thanks again all for your help.

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