From nobody Fri Aug 9 17:05:44 2024 X-Original-To: freebsd-usb@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WgVgB1sfJz5SR6r for ; Fri, 09 Aug 2024 17:06:14 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WgVgB1NJmz40x1 for ; Fri, 9 Aug 2024 17:06:14 +0000 (UTC) (envelope-from hrs@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1723223174; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=SCFI+vY9Ydek9MbeCsuwGeg6wSFp3kWaUVqf5yTnU+U=; b=xgmcQG/WPrqW374bzFpPFsM3MBKAJOzYRteRS2NXTmxrccHM+GOnHkRS1bdraK5LlLx2vP s3v0U6dcAUQWN6y/bbp16fTil/JAefGoaMGwO+cJXPbm67HGEM/fDwbkHzUAOQiYokdDRz Bk9tMD/Oh1zxNQrP02txdt6Em/RtnU8kr3jabREwDkMAhq1VKMu2IeVeWjyowrHf7l8WVZ cQRhlAx7iIudTRWRR0SWRQ7ugQCe6yYOI/OSouJoR0Blc/Ko3m47gsr6HvsvuReyzeL0bv 00JncWzv3MG00QCwaplyHnCZ0eE7xXvk6uRyPepsaZuzcNzhGqvpumFWR6zsZQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1723223174; a=rsa-sha256; cv=none; b=QXp7WIP3ydqrvISYUIgIXUYP6uwesi1ouu/W0/Icw2nRfKbDJeo308JSN3doLlIBSVnWhW XB38Xw37cZN72ZfBJbJ5FNsYtSq70rzfPVqfDAJDZtyOxRemjcMekH7rYUTWR6Dqt68HLt T7me55AvfJT7Oml95PN6iYTUarYKCpe7TW49bFcXdPwRxO97O0x2BqgkN/2bCp7taXQ5FA /sVA1+V9TcNi70r9fZtAifxxibI9ASxCZhG6OGoMRcoA6YxliTy99NRmIjzLwd1MxDeal8 28h0VpzHqcWtT799gwVMx+HAsvoTBIuB2tXbwlfkm3S/0NVWEOS4tFFB2SydNQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1723223174; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=SCFI+vY9Ydek9MbeCsuwGeg6wSFp3kWaUVqf5yTnU+U=; b=aWA2VfyoYBXhoeIRuN2nNEFWOKEvUCiDRSxpBsqJgYzcKE2B9hdcv8QFTdWn2S2QuNsYqd AujjVKVSgjM7to32YgdKT2uIeVGcjxAzS00nQpRL8obytjGXEybDjqca6B0xQlLM6ec3LI Nrzxt5TnmoivkJHiyQDzl+ze29+jSDR7Y9G/Aofae+drdxC+1IFM0TYDAHEUh0c5zaBfOc 88QhCS3BqVXXEQriH1AFNMj08HBUz6fjJTOYheqTyvQlC70kUXQ1ASkIlHyONqZreeKEWp uVBkLQaQt0NvJ3eG5W98RQyQzJ9NTZoyCjEUP26QqJHilwZz9m9++qhIeniEJg== Received: from localhost (unknown [IPv6:2400:4051:a743:3c00:5a9c:fcff:fe10:ffc2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: hrs) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WgVg94JYszY3l for ; Fri, 9 Aug 2024 17:06:13 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Date: Sat, 10 Aug 2024 02:05:44 +0900 (JST) Message-Id: <20240810.020544.1793914533481406393.hrs@FreeBSD.org> To: freebsd-usb@freebsd.org Subject: [CFT] USB xHCI DbC console on amd64 From: Hiroki Sato X-Old-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-PGPkey-fingerprint: 6C0D 2353 27CF 80C7 901E FDD2 DBB0 7DC6 6F1F 737F X-Mailer: Mew version 6.8 on Emacs 28.2 List-Id: FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-usb List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-usb@freebsd.org Sender: owner-freebsd-usb@FreeBSD.org Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha512; boundary="--Security_Multipart(Sat_Aug_10_02_05_44_2024_524)--" Content-Transfer-Encoding: 7bit ----Security_Multipart(Sat_Aug_10_02_05_44_2024_524)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I would like more people to test the xHCI debug console driver since I finally confirmed that it worked stably on most machines with Type-A USB 3.0 ports. While the patchset is not commit-ready yet due to some rough edges, you can use bootable USB memory images or temporarily replace the kernel and loader on your environment to test console access on the UEFI loader, kernel after boot, and via a tty device from the userland. Test instructions can be found at https://wiki.freebsd.org/HirokiSato/xhci and the URLs for bootable images (based on stable/14 at this moment) are available on the same page. As described there, my patchset can also be found in my Github repo. If it worked (or did not work), please report it to the freebsd-usb@ mailing list for now. I will update the repo and bootable images if there is any progress. Note that you need at least a USB3 A-to-A cross cable for testing. I am not sure how well compatible cables are available in the market, but I have distributed confirmed cables at conferences. If you are interested in it, please catch me somewhere. I will be at EuroBSDcon in September at the earliest. Also note that machines with only Type-C ports (especially on and after 12th-gen Intel processors) are likely not to recognize the A-to-A cable even if using an A-to-C adapter at this moment, while the xHCI controller supports the debug feature itself. It seems that the OS needs to control the role of a Type-C USB port because Type-C ports on a machine are usually configured to work as a USB host, not a USB device. I am investigating drivers of Intel UCSI, PMC Mux, xDCI, and DWC3 found at legacy Intel processors. -- Hiroki ----Security_Multipart(Sat_Aug_10_02_05_44_2024_524)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iMkEABMKAC4WIQRsDSNTJ8+Ax5Ae/dLbsH3Gbx9zfwUCZrZMaBAcaHJzQGZyZWVi c2Qub3JnAAoJENuwfcZvH3N/BVICCQFGQK3gcgEhJLfJt242LnKVmstn3sr7oIkW vy4ACvHBAC8/ByKXTq4coXhUA4PYt2hdpBJfUiw/rEIgiJ5wBcZJhAIIv1iEPTTf CSqDquS8aLbGZg/Easj/eIfquqbARxNwYTevJzE1hAcypnEwf6UgcfnPuetJXJo/ gNsFcSQDTqJAX1g= =O5IP -----END PGP SIGNATURE----- ----Security_Multipart(Sat_Aug_10_02_05_44_2024_524)----