What steps will reproduce the problem?
1.
Rowboat version:rowboat-froyo.xml - for froyo version of rowboat
2.
make TARGET_PRODUCT=am3517crane OMAPES=3.x -j4
Booting Rowboat android from MMC SD success
3.
logcat information:
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
android init
android_probe pdata: c04311f8
android_bind
android_usb gadget: android_usb ready
f_adb init
android_register_function adb
adb_bind_config
f_mass_storage init
android_register_function usb_mass_storage
using rtc device, tps65910_rtc, for alarms
tps65910_rtc tps65910_rtc: rtc core: registered tps65910_rtc as rtc0
TPS65910 RTC device successfully registered
Linux video capture interface: v2.00
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
davinci_emac_probe: using random MAC addr: 1e:70:a6:2a:da:6a
emac-mii: probed
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SU08G 7.40 GiB
mmcblk0:
usb 1-1: new high speed USB device using ehci-omap and address 2
tps65910_rtc tps65910_rtc: setting system clock to 2000-01-03 05:56:12 UTC
(946878972)
Waiting 1sec before mounting root device...
p1 p2 p3
usb 1-1: New USB device found, idVendor=05e3, idProduct=0606
usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-1: Product: USB2.0 Hub
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.4: new low speed USB device using ehci-omap and address 3
usb 1-1.4: New USB device found, idVendor=045e, idProduct=00cb
usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4: Product: Microsoft Basic Optical Mouse v2.0
usb 1-1.4: Manufacturer: Microsoft
input: Microsoft Microsoft Basic Optical Mouse v2.0 as
/devices/platform/ehci-omap.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input0
generic-usb 0003:045E:00CB.0001: input: USB HID v1.11 Mouse [Microsoft
Microsoft Basic Optical Mouse v2.0 ] on usb-ehci-omap.0-1.4/input0
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 160K
Warning: unable to open an initial console.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
# enabling adb
adb_open
warning: `zygote' uses 32-bit capabilities (legacy support in use)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, id=7c0f1)
binder: release 975:975 transaction 1208 out, still active
binder: transaction release 1308 bad object type 1c
binder: 825:825 transaction failed 29189, size 4-0
binder: send failed reply for transaction 1208, target dead
What is the expected output? What do you see instead?
/////////////////////////////
/i hope visible mouse cursor/
/////////////////////////////
#getevent
add device 1: /dev/input/event0
name: "Microsoft Microsoft Basic Optical Mouse v2.0 "
/dev/input/event0: 0004 0004 00090002
/dev/input/event0: 0001 0111 00000001
/dev/input/event0: 0000 0000 00000000
/dev/input/event0: 0004 0004 00090002
/dev/input/event0: 0001 0111 00000000
/dev/input/event0: 0000 0000 00000000
What version of the product are you using? On what operating system?
Rowboat version:rowboat-froyo.xml
Please provide any additional information below.
/////////////////////////////
/i hope visible mouse cursor/
/////////////////////////////
Thanks!!
Original issue reported on code.google.com by MYChen0...@gmail.com on 18 Apr 2011 at 12:15
Original issue reported on code.google.com by
MYChen0...@gmail.comon 18 Apr 2011 at 12:15