From owner-freebsd-current@FreeBSD.ORG Wed Oct 1 19:12:25 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 209BD256 for ; Wed, 1 Oct 2014 19:12:25 +0000 (UTC) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AAB7392F for ; Wed, 1 Oct 2014 19:12:24 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id a1so1308910wgh.33 for ; Wed, 01 Oct 2014 12:12:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=CSIDatsNu/jtsKqCagwXKJ0RVnbw7yUXnfRYPK+MzE8=; b=VMa/3bT9S6lw8fd4NcjMIKMSUv/lqA5JgRoWLq3f37bV/C73RFOiShFKzvevkgKiGd MZ3QK3eWbRL8FiWYnroD2Jk8k3YRklCL96DregNbK7d1j9bJvoIwvnfJnm3yaeKcMH6o aAf32RDhRZTrUiWDrG0XyCGVDQwaOf0TADIX2HwmyorMwk0xFUq/zi9L+hAj9aU0jFrk BZOl3EdmHvG3+HPgalqW5srkCHy7y4ZsBhsTKkvSenUmLixjYATjHmZZiXPqfncfsqEz KCFHZ505JX11AX7xoaUcQmODxftvdHPfDvBmednUTZUOX2s518vmUrvCzGiLIR5yx0Ob NF5w== MIME-Version: 1.0 X-Received: by 10.180.101.129 with SMTP id fg1mr16885338wib.20.1412190742918; Wed, 01 Oct 2014 12:12:22 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Wed, 1 Oct 2014 12:12:22 -0700 (PDT) In-Reply-To: <542BD381.4090808@selasky.org> References: <20140928071641.M7664@beckpeccoz.com> <20140929003358.M78145@aoek.com> <542AC1C8.9030101@freebsd.org> <90CE0701-F1CB-41DF-B3D2-87816DC03DF9@emc.com> <542BD381.4090808@selasky.org> Date: Wed, 1 Oct 2014 12:12:22 -0700 X-Google-Sender-Auth: ZkkOajCAK0C7OOcdW5IQnZkZ0g4 Message-ID: Subject: Re: What do you use for kernel debugging? From: Adrian Chadd To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: "O'Connor, Daniel" , FreeBSD Current , Benjamin Kaduk , Garrett Cooper , =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez_Arauzo?= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 19:12:25 -0000 On 1 October 2014 03:12, Hans Petter Selasky wrote: > On 10/01/14 07:03, Adrian Chadd wrote: >> >> There's also something for XHCI. >> >> Please please write it for freebsd. :) >> >> > > Hi, > > The FreeBSD bootloader can run a regular USB stack which connects to the > XHCI/EHCI and any supported serial adapter for example. What is currently > missing is some PCI pieces to attach the drivers. You don't need the USB > debug port to get keyboard/console input. We actually _want_ the debug port support. The EHCI/XHCI debugging stuff is separate from the whole normal USB stack and is really designed for lower level debugging - ie, when everything is actually busted. Think of it as being the polled conduit for doing remote kgdb and (hopefully, with the XHCI stuff) remote memory inspection when things go off the deep end. -a