DM365: Problem of using filesystem made by own
chris-meng at ti.com
Fri Jul 9 02:27:34 CDT 2010
We are facing problem to using filesystem made by own. When the DM365 system boots up with new FS by NFS, /dev/video0, /dev/video2, /dev/video3 can be generated. And /dev/video2, /dev/video3 can be opened correctly. But if open video0, there is error as below.
kobject_add failed for (-13)
Failed to register TVP7002<http://focus-webapps.ti.com/general/docs/sitesearch/searchdevice.tsp?partNumber=tvp7002> I2C client.
vpfe ccdc capture vpfe ccdc capture.1: Error in initializing channel
open fd is error
The busybox version used is 18.104.22.168. Using the FS provided in DVSDK2.1 is ok.
Would you pls kindly advise what is missed?
Have you ever made FS for DM365? Would you pls share with me the configuration file for busybox? We suspected the problem is due to the configuration.
The filesystem made by own can't use below inittab which is in the FS provided in DVSDK2.1 (See detail below). Why? Is this due to the configuration of busybox?
Any comment is appreciated!
# /etc/inittab: init(8) configuration.
2 # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
4 # The default runlevel.
7 # Boot-time system configuration/initialization script.
8 # This is run first except when booting in emergency (-b) mode.
11 # What to do in single-user mode.
14 # /etc/init.d executes the S and K scripts upon change
15 # of runlevel.
17 # Runlevel 0 is halt.
18 # Runlevel 1 is single-user.
19 # Runlevels 2-5 are multi-user.
20 # Runlevel 6 is reboot.
22 l0:0:wait:/etc/init.d/rc 0
23 l1:1:wait:/etc/init.d/rc 1
24 l2:2:wait:/etc/init.d/rc 2
25 l3:3:wait:/etc/init.d/rc 3
26 l4:4:wait:/etc/init.d/rc 4
27 l5:5:wait:/etc/init.d/rc 5
28 l6:6:wait:/etc/init.d/rc 6
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Davinci-linux-open-source