android init
android_probe pdata: c06ccbf0
android_bind
android_usb gadget: android_usb ready
s3c-hsotg s3c-hsotg: new device is full-speed
s3c-hsotg s3c-hsotg: s3c_hsotg_irq: USBRst
s3c-hsotg s3c-hsotg: EP0: DIEPCTL0=0x00008000, DOEPCTL0=0x80008000
s3c-hsotg s3c-hsotg: DCTL=0x00000002
s3c-hsotg s3c-hsotg: EP0: DIEPCTL0=0x00008000, DOEPCTL0=0x80008000
s3c-hsotg s3c-hsotg: S3C_GINTSTS_USBSusp
s3c-hsotg s3c-hsotg: s3c_hsotg_irq: USBRst
s3c-hsotg s3c-hsotg: bound driver android_usb
f_adb init
android_register_function adb
f_mass_storage init
fsg_probe pdev: c06cc810, pdata: c06ccb78
android_register_function usb_mass_storage
android_usb gadget: Mass Storage Function, version: 2009/09/11
android_usb gadget: Number of LUNs=1
lun0: LUN: removable file: (no medium)
adb_bind_config
mice: could not register psaux device, error: -16
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
S3C Touchscreen driver, (c) 2010 FriendlyARM
touchscreen got loaded successfully : 12 bits
touchscreen-1wire initialized
backlight-1wire initialized
input: TouchScreen Pipe as /devices/virtual/input/input1
ts-if initialized
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling
using rtc device, s3c, for alarms
s3c-rtc s3c64xx-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver usbvision
USBVision USB Video Device Driver for Linux : 0.9.10
usbcore: registered new interface driver pvrusb2
pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
pvrusb2: Debug mask is 31 (0x1f)
usbcore: registered new interface driver zr364xx
zr364xx: Zoran 364xx
one_wire_status: 4
usbcore: registered new interface driver stkwebcam
gspca: main v2.10.0 registered
usbcore: registered new interface driver hdpvr
usbcore: registered new interface driver s2255
s3c-fimc: controller 0 registered successfully
s3c-fimc: controller 1 registered successfully
FIMC Driver, 2010 ported by FriendlyARM
http://www.arm9.netov965x: probe
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
one_wire_status: 4
s3c-fimc: i2c transfer error
s3c-fimc: ov965x: Product ID fb:fb Manufacturer ID fb:fb
parent clock for camera: 266.000 MHz, divisor: 11
[CAM]RESET CAM.
S3C PostProcessor Driver v3.12, (c) 2009 Samsung Electronics
S3C6410 TV encoder Driver, (c) 2008 Samsung Electronics
S3C6410 TV encoder Driver init OK.
S3C6410 TV scaler Driver, (c) 2008 Samsung Electronics
S3C6410 TV scaler Driver init OK.
S3C JPEG Driver, (c) 2007 Samsung Electronics
one_wire_status: 4
s3c-g2d: Driver loaded succesfully
s3c-g2d: Module initialized.
s3c_g3d: clock enabled
s3c-g3d: detected FIMG-3DSE version 1.5.0
s3c-g3d: Driver loaded succesfully
s3c-g3d: Module initialized.
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCILL protocol initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
one_wire_status: 2
usbcore: registered new interface driver btusb
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133000000 Hz)
one_wire_status: 4
s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: mmc_bus (24000000 Hz)
s3c6400_setup_sdhci_cfg_card: CTRL 2=c0004120, 3=80808080
one_wire_status: 2
mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
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'
asoc: AC97 HiFi <-> s3c-ac97 mapping ok
s3c6400_setup_sdhci_cfg_card: CTRL 2=c0004100, 3=00008080
mmc0: new high speed SDHC card at address 0002
mmcblk0: mmc0:0002 00000 3.74 GiB
mmcblk0: p1
s3c6400_setup_sdhci_cfg_card: CTRL 2=c0004120, 3=80808080
ALSA device list:
#0: MINI6410 (WM9713)
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.15
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
one_wire_status: 2
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
one_wire_status: 4
s3c-rtc s3c64xx-rtc: hctosys: invalid date/time
eth0: link down
IP-Config: Complete:
device=eth0, addr=192.168.1.70, mask=255.255.255.0, gw=192.168.1.1,
host=mini6410, domain=, nis-domain=arm9.net,
bootserver=192.168.1.111, rootserver=192.168.1.111, rootpath=
Freeing init memory: 1396K
mount: RPC: Remote system error - No route to host
1Wire touchscreen OK
/init: line 103: can't open /r/dev/console: no such file
Kernel panic - not syncing: Attempted to kill init!
[<c016a9a4>] (unwind_backtrace+0x0/0xe4) from [<c050a9d8>] (panic+0x68/0x194)
[<c050a9d8>] (panic+0x68/0x194) from [<c01827e4>] (do_exit+0x68/0x664)
[<c01827e4>] (do_exit+0x68/0x664) from [<c018310c>] (do_group_exit+0xb0/0xe4)
[<c018310c>] (do_group_exit+0xb0/0xe4) from [<c0183150>] (sys_exit_group+0x10/0x18)
one_wire_status: 2
[<c0183150>] (sys_exit_group+0x10/0x18) from [<c0165e60>] (ret_fast_syscall+0x0/0x30)
Rebooting in 5 seconds..one_wire_status: 4
如题，Tiny6410开发板可以在PC上挂载Android文件系统吗？
我在挂载Android文件系统时出现以上错误，Android文件系统是友善官方的，不知道是什么原因？
望高手指点！
