6 Dec
2006
6 Dec
'06
10:24 p.m.
\
- Host, to which that console connects (through the debug device); runs usb_debug, much like any other usb-serial device
My understanding was that the client could run in user space only on top of libusb.
It's analagous to debugging an embedded box using a serial console with a Linux host ... except the target here is a PC, not an ARM (or PPC, MIPS, etc) custom board.
Once the coexistence issues between the debug port and normal EHCI driver get worked, there's no reason not to keep using that debug port as a system console.
One reason is the one I covered in my last mail -- locking of the PCI type 1 ports.
However I suppose it would be ok to switch Eric's code between early pci access and locked one once the PCI subsystem is up and running. Just don't forget bust_spinlocks()
-Andi