tiny210V2开发板hdmi输出到10.1寸LCD，无图像

[ 2.264018] USB Serial support registered for GSM modem (1-port)

[ 2.270103] usbcore: registered new interface driver option

[ 2.275435] option: v0.7.2:USB Driver for GSM modems

[ 2.280456] USB Serial support registered for oti6858

[ 2.287519] usbcore: registered new interface driver oti6858

[ 2.291129] USB Serial support registered for pl2303

[ 2.296106] usbcore: registered new interface driver pl2303

[ 2.301528] pl2303: Prolific PL2303 USB to serial adaptor driver

[ 2.307596] USB Serial support registered for qcaux

[ 2.313477] usbcore: registered new interface driver qcaux

[ 2.319914] USB Serial support registered for Qualcomm USB modem

[ 2.323941] usbcore: registered new interface driver qcserial

[ 2.329521] safe_serial: v0.1:USB Safe Encapsulated Serial

[ 2.335056] USB Serial support registered for safe_serial

[ 2.340466] usbcore: registered new interface driver safe_serial

[ 2.346432] USB Serial support registered for siemens_mpi

[ 2.351821] usbcore: registered new interface driver siemens_mpi

[ 2.357684] Driver for Siemens USB/MPI adapter

[ 2.362087] Version 0.1 09/26/2005 Thomas Hergenhahn@web.de http://libnodave.sf.net

[ 2.369810] USB Serial support registered for Sierra USB modem

[ 2.375663] usbcore: registered new interface driver sierra

[ 2.381063] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems

[ 2.387645] USB Serial support registered for SPCP8x5

[ 2.394740] usbcore: registered new interface driver spcp8x5

[ 2.398220] spcp8x5: v0.10:SPCP8x5 USB to serial adaptor driver

[ 2.404198] USB Serial support registered for Quatech SSU-100 USB to Serial Driver

[ 2.411789] usbcore: registered new interface driver ssu100

[ 2.417216] ssu100: v0.1:Quatech SSU-100 USB to Serial Driver

[ 2.424018] USB Serial support registered for symbol

[ 2.430020] usbcore: registered new interface driver symbol

[ 2.433526] USB Serial support registered for TI USB 3410 1 port adapter

[ 2.440197] USB Serial support registered for TI USB 5052 2 port adapter

[ 2.446890] usbcore: registered new interface driver ti_usb_3410_5052

[ 2.453180] ti_usb_3410_5052: v0.10:TI USB 3410/5052 Serial Driver

[ 2.459435] USB Serial support registered for Handspring Visor / Palm OS

[ 2.466108] USB Serial support registered for Sony Clie 3.5

[ 2.471654] USB Serial support registered for Sony Clie 5.0

[ 2.477223] usbcore: registered new interface driver visor

[ 2.482559] visor: USB HandSpring Visor / Palm OS driver

[ 2.487933] USB Serial support registered for Connect Tech - WhiteHEAT - (prerenumeration)

[ 2.496159] USB Serial support registered for Connect Tech - WhiteHEAT

[ 2.504703] usbcore: registered new interface driver whiteheat

[ 2.508361] whiteheat: v2.0:USB ConnectTech WhiteHEAT driver

[ 2.514079] USB Serial support registered for vivopay-serial

[ 2.519755] usbcore: registered new interface driver vivopay-serial

[ 2.525886] vivopay_serial: v1.0:ViVOpay USB Serial Driver

[ 2.532425] USB Serial support registered for zio

[ 2.538123] usbcore: registered new interface driver zio

[ 2.541313] Initializing USB Mass Storage driver...

[ 2.546306] usbcore: registered new interface driver usb-storage

[ 2.552141] USB Mass Storage support registered.

[ 2.556884] s3c-udc : S3C HS USB Device Controller Driver, (c) 2008-2009 Samsung Electronics

[ 2.556890] s3c-udc : version 15 March 2009 (DMA Mode)

[ 2.572589] android_usb gadget: Mass Storage Function, version: 2009/09/11

[ 2.577105] android_usb gadget: Number of LUNs=1

[ 2.581762] lun0: LUN: removable file: (no medium)

[ 2.586836] android_usb gadget: android_usb ready

[ 2.606387] Registered gadget driver 'android_usb'

[ 2.606708] mousedev: PS/2 mouse device common for all mice

[ 2.607209] touchscreen-1wire initialized

[ 2.607245] backlight-1wire initialized

[ 2.609369] setup_irq: ret = 0

[ 2.612360] PWM clock = 66700000

[ 2.616581] TCNT_FOR_SAMPLE_BIT = 3472, TCFG1 = 00000000

[ 2.623198] input: fa_ts_input as /devices/virtual/input/input0

[ 2.627226] ts-if initialized

[ 2.629992] S3C24XX RTC, (c) 2004,2006 Simtec Electronics

[ 2.635181] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling

[ 2.640504] 2: TCNTB=00000d90, TCNTO=00000656, TINT_CSTAT=00000008

[ 2.646673] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling

[ 2.652166] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling

[ 2.657614] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling

[ 2.663030] 4: TCNTB=00000d90, TCNTO=000001f3, TINT_CSTAT=00000008

[ 2.669206] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling

[ 2.675048] using rtc device, s3c, for alarms

[ 2.678857] s3c-rtc s3c64xx-rtc: rtc core: registered s3c as rtc0

[ 2.685191] i2c /dev entries driver

[ 2.689128] Linux video capture interface: v2.00

[ 2.693195] mfc_init: <6>S5PC110 MFC Driver, (c) 2009 Samsung Electronics

[ 2.693200]

[ 2.704217] S3C JPEG Driver, (c) 2007 Samsung Electronics

[ 2.706684] JPEG driver for S5PV210

[ 2.710638] i2c i2c-1: attached s5p_ddc into i2c adapter successfully

[ 2.716686] S5PC11X HPD Driver, (c) 2010 Samsung Electronics

[ 2.722504] S5PC11X CEC Driver, (c) 2010 Samsung Electronics

[ 2.728756] usbcore: registered new interface driver uvcvideo

[ 2.733547] USB Video Class driver (v1.1.0)

[ 2.779457] input: mma7660 as /devices/platform/s3c2440-i2c.0/i2c-0/0-004c/input/input1

[ 2.779729] mma7660 0-004c: MMA7660 device is probed successfully.

[ 2.779897] i2c-core: driver [mma7660] using legacy suspend method

[ 2.779950] i2c-core: driver [mma7660] using legacy resume method

[ 2.783548] MMA7660 sensor driver registered.

[ 2.787873] S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics

[ 2.794029] s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled

[ 2.802335] device-mapper: uevent: version 1.0.3

[ 2.806410] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com

[ 2.814418] Bluetooth: HCI UART driver ver 2.2

[ 2.818811] Bluetooth: HCI H4 protocol initialized

[ 2.823581] Bluetooth: HCILL protocol initialized

[ 2.828408] cpuidle: using governor ladder

[ 2.832536] cpuidle: using governor menu

[ 2.842867] usbcore: registered new interface driver usbhid

[ 2.842918] usbhid: USB HID core driver

[ 2.846731] ALSA device list:

[ 2.848532] No soundcards found.

[ 2.851911] oprofile: hardware counters not available

[ 2.856937] oprofile: using timer interrupt.

[ 2.861293] GACT probability NOT on

[ 2.864656] Mirror/redirect action on

[ 2.868291] u32 classifier

[ 2.870975] Actions configured

[ 2.874358] Netfilter messages via NETLINK v0.30.

[ 2.879096] nf_conntrack version 0.5.0 (6154 buckets, 24616 max)

[ 2.885888] ctnetlink v0.93: registering with nfnetlink.

[ 2.890347] NF_TPROXY: Transparent proxy support initialized, version 4.1.0

[ 2.897238] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.

[ 2.903379] xt_time: kernel timezone is -0000

[ 2.908859] ip_tables: (C) 2000-2006 Netfilter Core Team

[ 2.912809] arp_tables: (C) 2002 David S. Miller

[ 2.917306] TCP cubic registered

[ 2.921405] NET: Registered protocol family 10

[ 2.929524] Mobile IPv6

[ 2.929577] ip6_tables: (C) 2000-2006 Netfilter Core Team

[ 2.932902] IPv6 over IPv4 tunneling driver

[ 2.941203] NET: Registered protocol family 17

[ 2.941277] NET: Registered protocol family 15

[ 2.945798] Bluetooth: RFCOMM TTY layer initialized

[ 2.950529] Bluetooth: RFCOMM socket layer initialized

[ 2.955647] Bluetooth: RFCOMM ver 1.11

[ 2.959367] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[ 2.964653] Bluetooth: HIDP (Human Interface Emulation) ver 1.2

[ 2.970773] NET: Registered protocol family 35

[ 2.975069] Registering the dns_resolver key type

[ 2.979672] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2

[ 2.987272] ThumbEE CPU extension supported.

[ 2.991718] s5pv210_cpufreq_init: S5PV210 cpu-freq driver

[ 2.997446] regulator_init_complete: pd_mfc_supply: disabling

[ 3.002615] regulator_init_complete: pd_tv_supply: disabling

[ 3.008296] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling

[ 3.013723] s3c-rtc s3c64xx-rtc: setting system clock to 2013-07-08 07:08:09 UTC (1373267289)

[ 3.024674] FIMC0 registered successfully

[ 3.027566] FIMC1 registered successfully

[ 3.031511] FIMC2 registered successfully

[ 3.034278] S5PC1XX TVOUT Driver, (c) 2009 Samsung Electronics

[ 3.040515] s5p-tvout s5p-tvout: hpd status is cable inserted

[ 3.052201] Freeing init memory: 1456K

[ 3.059511] yaffs: dev is 32505860 name is 'mtdblock4' rw

[ 3.059562] yaffs: passed flags ''

[ 22.588472] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling

[07/Jul/2013:23:08:30 +0000] boa: server version Boa/0.94.13

[07/Jul/2013:23:08:30 +0000] boa: server built Dec 30 2010 at 11:18:35.

[07/Jul/2013:23:08:30 +0000] boa: starting server pid=1081, port 80

[ 25.807512] FriendlyARM http://www.arm9.net

[ 25.920468] asoc: wm8960-hifi <-> samsung-i2s.0 mapping ok

[ 26.472953]

[ 26.472959] rtw driver version=v3.3.2_3192.20120103

[ 26.473018] ##########rtw_suspend_lock_init ###########

[ 26.476654] usbcore: registered new interface driver rtl8192cu

Try to bring eth0 interface up......[ 26.531099] dm9000 dm9000: eth0: link down

[ 26.531392] ADDRCONF(NETDEV_UP): eth0: link is not ready

Done

Please press Enter to activate this console. [ 36.126804] same hpd_status value: 1

[ 38.666094] same hpd_status value: 1

[ 41.209161] same hpd_status value: 1

[ 42.131424] same hpd_status value: 1

[ 47.208807] same hpd_status value: 1

[ 48.146228] same hpd_status value: 1

[ 53.228286] same hpd_status value: 1

[ 60.253407] same hpd_status value: 1

[ 62.713216] same hpd_status value: 1

[ 65.252198] same hpd_status value: 1

[ 78.204864] same hpd_status value: 1

[ 83.283177] same hpd_status value: 1

[ 89.295518] same hpd_status value: 1

[ 101.307078] same hpd_status value: 1

[ 107.326187] same hpd_status value: 1

[ 108.247903] same hpd_status value: 1

[ 114.259641] same hpd_status value: 1

[ 119.338330] same hpd_status value: 1

[ 120.279321] same hpd_status value: 1

[ 125.361196] same hpd_status value: 1

问题解决方法：

根据HDMI协议中的热拔插和检测原理可以知道，当接收设备第18脚被连通（H18），并接收到+5V电压时，

会把第19脚的HPD信号变为高电平，通知源端可以开始接收带有接收端设备各种信息的E-EDID数

据（Enhanced Extended Display Identification Data），此时源端则可以开始

通过DDC（Display Data Channel）接收E-EDID信息。至此，源端和接收端之间的初始化完毕，

并在二者之间建立了一条数据通道。?????

在此通道建立以后，设备是否能够自动跳转到HDMI发送/接收状态则需要由设备本身的软件来进行控制，

“热插拔”只能够起到建立物理连接的作用。

然后根据打印信息，查看友善提供的源码可以知道，后面总是出现这种打印信息想原因是因为HDMI总是进入中