On Wed, Dec 28, 2011 at 01:55:07PM -0500, Curtis.Cyran@xxxxxxxxx wrote: > Sarah, > > Thanks for looking into this for me. As I stated in my original email to > you, I'm stuck at kernel version 2.6.37 due to the software support from > the manufacturer of the embedded device. 2.6.37 a year old. You should ask your manufacturer to get their patches upstream so you can use a later version. Have you just tried the 3.1.6 kernel? It's possible someone else has gotten the support for your board upstream. > Attached is the output of dmesg. Please let me know if you need any > additional information. > > If you see anything obvious, let me know. My intention is not to rewrite > the usb section of kernel version 2.6.37. I am primarily interested in > knowing if I am a small patch or configuration setting away from having > this work properly. There's nothing really useful there. The xHCI driver issued a command, and your log file doesn't show whether the host responded or not (maybe you didn't wait long enough before stopping the log?). > xhci_hcd 0000:01:00.0: set port power, actual port 3 status = 0x202e1 > xhci_hcd 0000:01:00.0: get port status, actual port 0 status = 0x2a0 > xhci_hcd 0000:01:00.0: Get port status returned 0x100 > xhci_hcd 0000:01:00.0: get port status, actual port 1 status = 0x2a0 > xhci_hcd 0000:01:00.0: Get port status returned 0x100 > xhci_hcd 0000:01:00.0: get port status, actual port 2 status = 0x2a0 > xhci_hcd 0000:01:00.0: Get port status returned 0x100 > xhci_hcd 0000:01:00.0: get port status, actual port 3 status = 0x202e1 > xhci_hcd 0000:01:00.0: Get port status returned 0x10101 > xhci_hcd 0000:01:00.0: `MEM_WRITE_DWORD(3'b000, 32'hd0990450, 32'h202e1, 4'hf); > xhci_hcd 0000:01:00.0: clear port connect change, actual port 3 status = 0x2e1 > xhci_hcd 0000:01:00.0: get port status, actual port 3 status = 0x2e1 > xhci_hcd 0000:01:00.0: Get port status returned 0x101 > xhci_hcd 0000:01:00.0: Endpoint state = 0x1 > xhci_hcd 0000:01:00.0: Command ring enq = 0x8be2a020 (DMA) > xhci_hcd 0000:01:00.0: // Ding dong! > xhci_hcd 0000:01:00.0: `MEM_WRITE_DWORD(3'b000, 32'hd0990800, 32'h0, 4'hf); > NET: Registered protocol family 10 > SysLink version : 2.00.05.85 > SysLink module created on Date:Dec 28 2011 Time:11:32:38 > HDMI W1 rev 2.0 > Timing Info: > pixel_clk = 148500 > x_res = 1920 > y_res = 1080 > hfp = 88 > hsw = 44 > hbp = 148 > vfp = 4 > vsw = 5 > vbp = 36 > hdmi: Enter HDMI_W1_StopVideoFrame() > hdmi: Enter HDMI_W1_GlobalInitVars() > hdmi: Enter HDMI_Core_GlobalInitVars() > hdmi: Enter HDMI_W1_ConfigVideoInterface() > hdmi: HDMI_WP_AUDIO_CFG = 0x1030006 > hdmi: HDMI_WP_AUDIO_CFG2 = 0x20c0 > hdmi: HDMI_WP_AUDIO_CTRL = 0x20 > hdmi: Enter DSS_HDMI_CORE_SW_RESET_ASSERT () > hdmi: Enter DSS_HDMI_CORE_POWER_DOWN_DISABLE() > hdmi: Enter DSS_HDMI_CORE_SW_RESET_RELEASE() > hdmi: Enter HDMI_W1_StartVideoFrame () > eth0: no IPv6 routers present > root@dm816x-evm:~# Is there anything about "Timed out" from the xHCI driver later in the log? Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
