All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christian Tramnitz <chris.ace@gmx.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: debugging Xen in a serial-less environment
Date: Sat, 07 Mar 2009 01:48:49 -0800	[thread overview]
Message-ID: <49B24301.6020609@goop.org> (raw)
In-Reply-To: <gotcgl$mkb$1@ger.gmane.org>

Christian Tramnitz wrote:
> But it seems to be a bit harder to find those dongles. It look like 
> the only model (NET20DC) isn't RoHS compliant which explains why I 
> don't find a place to order them in Eruope.
> But other than that this seems to be a good long-term alternative to a 
> serial console. I haven't looked at the code for it in the linux 
> kernel but does anyone know if it's required to get all the hcd and 
> usbcore stuff loaded before being able to use the debug port? If not, 
> whats the behaviour of the usb bus (and the debug port) when those 
> drivers are loaded by dom0 subsequently? 

It appears that the USB hardware has a special simplified PIO 
programming mode that is relatively easy to operate without the full USB 
stack in place.  But there's a comment in the Linux code to the effect 
that you can't keep a debug port early console because the full USB 
stack will subsequently reset and take over the hardware.

In Xen I'm guessing that means that you'd have to dedicate a USB 
controller to debug output and prevent dom0 from using it.  Which seems 
a bit inconvenient.

    J

      reply	other threads:[~2009-03-07  9:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 21:43 debugging Xen in a serial-less environment Christian Tramnitz
2009-03-04 21:50 ` Dugger, Donald D
2009-03-05  9:42 ` Gerd Hoffmann
2009-03-06 19:33   ` Jeremy Fitzhardinge
2009-03-07  8:50     ` Christian Tramnitz
2009-03-07  9:48       ` Jeremy Fitzhardinge [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49B24301.6020609@goop.org \
    --to=jeremy@goop.org \
    --cc=chris.ace@gmx.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.