or usb_debug that Greg just added
Ah I didn't notice that. If there is a usb_debug that works later then yes it would need to be disabled.
I detect confusion here ... remember that there are potentially two distinct Linux systems involved here:
- Target, with some kind of console hooked up to the debug device; runs this _new_ "early debug port" code.
- Host, to which that console connects (through the debug device); runs usb_debug, much like any other usb-serial device
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. Heck, being able to do that might be a huge win with some of the nasty suspend/resume problems we've got.
- Dave