Sorry for the late response, as I do not follow linux-usb list very closely.
I have discussed recent Intel chipsets and EHCI debug in some detail on
the coreboot mailing list [1].
As for the discussion [2] that took place here in February, I noticed
you tried with early_printk=dbgp which
,
Linux kernel (3.12.8) fails to setup EHCI debug port on my Sandy Bridge
server. This seems to be a normal thing as I tried on other machines and got
the same result.
Do you have a EHCI debug connector to attach to it? That is required in
you can make one, if you wish:
http://www.coreboot.org
On Wed, 19 Feb 2014, Lu, Baolu wrote:
Thanks for reply and help. I attached an Ajays NET20DC to the USB port.
It seems not help here.
Below is the dmesg and lsusb output.
[root@localhost ~]# uname -a
Linux localhost.localdomain 3.12.8 #2 SMP Tue Feb 18 06:09:46 CST 2014
x86_64 x86_64
It is quite possible that the debug port on this motherboard is not
wired to a USB connector. If that's true, the only way you will get
the debug device to work is by connecting it directly to a header on
the motherboard.
Is that likely to be the single USB header on many motherboards?
On Wed, 19 Feb 2014, David Laight wrote:
It is quite possible that the debug port on this motherboard is not
wired to a USB connector. If that's true, the only way you will get
the debug device to work is by connecting it directly to a header on
the motherboard.
Is that likely to be
On Tue, Feb 18, 2014 at 02:46:00PM +0800, Lu, Baolu wrote:
Hi list,
Linux kernel (3.12.8) fails to setup EHCI debug port on my Sandy Bridge
server. This seems to be a normal thing as I tried on other machines and got
the same result.
Do you have a EHCI debug connector to attach
On Tue, Feb 18, 2014 at 09:01:29AM -0800, Greg KH wrote:
On Tue, Feb 18, 2014 at 02:46:00PM +0800, Lu, Baolu wrote:
Hi list,
Linux kernel (3.12.8) fails to setup EHCI debug port on my Sandy Bridge
server. This seems to be a normal thing as I tried on other machines and got
the same
Hi list,
Linux kernel (3.12.8) fails to setup EHCI debug port on my Sandy Bridge
server. This seems to be a normal thing as I tried on other machines and
got the same result.
This is the EHCI host controller information (printed by lspci -vvv)
00:1a.0 USB controller: Intel Corporation C600
