Did you make, manually or in a script, a corresponding device file? > adb shell ls -l /dev/binder crw-rw-rw- 1 root root 10, 44 Sep 23 08:51 /dev/binder
If you aren't getting something similar you will need to mknod it On Sep 24, 3:42 am, siva ram krishna <[email protected]> wrote: > I am porting android on a ARM based platform.while booting android on > the target ,i am not able to get the display. > > the logcat shows the following information. > > I/DEBUG ( 1610): debuggerd: Dec 11 2007 13:22:03 > > D/AndroidRuntime( 1612): > > D/AndroidRuntime( 1612): >>>>>>>>>>>>>> AndroidRuntime START > <<<<<<<<<<<<<< > > I/runtime ( 1613): *** Startup: root='/system' asset='/system/app' > data='/data' *** > > I/runtime ( 1613): Can't find readable key input device > > W/runtime ( 1613): Invalid time detected, 13 set to 1167652800 > > E/ProcessState( 1613): Binder driver protocol does not match user > space protocol! > > E/ProcessState( 1613): Binder ioctl to set max threads failed: Bad > file number > > I/runtime ( 1613): Entered boot_init()! > > D/runtime ( 1613): ProcessState: 0x13408 > > I/runtime ( 1613): Binder driver not found. Processes not supported. > > I/ServiceManager( 1613): ServiceManager: addService(ui_hardware, > 0x13564) > > D/AndroidRuntime( 1613): > > D/AndroidRuntime( 1613): >>>>>>>>>>>>>> AndroidRuntime START <<<< > <<<<<<<<<< > > D/jdwp ( 1613): JDWP listening on port 8000 > > D/AndroidRuntime( 1613): --- registering native functions --- > > D/AndroidRuntime( 1612): --- registering native functions --- > > I/sysproc ( 1613): Entered system_init() > > I/sysproc ( 1613): ServiceManager: 0x13480 > > I/SurfaceFlinger( 1613): SurfaceFlinger is starting > > I/SurfaceFlinger( 1613): SurfaceFlinger's main thread ready to run. > Initializing graphics H/W... > > I/ ( 1613): *** About to switch to console 2. If the system > hangs, switch to console 2 manually (setconsole -v 2) > > F/SurfaceFlinger( 1613): FBIOGET_FSCREENINFO failed > > i have included the binder driver in the kernel while compiling ,but > the logcat shows binder driver not found. > > please suggest me to solve binder problem. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
