From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.groups.io with SMTP id smtpd.web11.169.1665068847681169119 for ; Thu, 06 Oct 2022 08:07:28 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=cgFBxi1A; spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665068846; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=eZxHFGHXyfUtjz+gSUKCnmWpBYuGl7rzwEEUCs6lAB4=; b=cgFBxi1AZ4wYt8CofFEUuOHNYlRdYr7R1eOkz5jvWAeV1/ArOAW1PXl294mgr/uylcNgDO EK70reViaDrYUDDLMeB6GM3rKKSB+o9GLeq2XX5qX4pM3h2Bal3llRVQdumMDOrHuWWC5x BUwPxXOIErI/5lD9Ru4npyb/RpcE9u4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-205-G_6S-NfLMiaY0CMqQKC2jg-1; Thu, 06 Oct 2022 11:07:23 -0400 X-MC-Unique: G_6S-NfLMiaY0CMqQKC2jg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2A097185A7A9; Thu, 6 Oct 2022 15:07:23 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (unknown [10.39.192.206]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A7ABB4047045; Thu, 6 Oct 2022 15:07:21 +0000 (UTC) Subject: Re: [edk2-devel] Intel NUC platform firmware -- no serial I/O support? From: "Laszlo Ersek" To: Gerd Hoffmann , devel@edk2.groups.io Cc: "Ramesh R." , Sivaraman Nainar , manickavasakam karpagavinayagam References: <4c8d982a-97b0-654c-c6db-9a55b95330b5@redhat.com> <20220407080008.o2qmtum4sxzw5zfo@sirius.home.kraxel.org> Message-ID: Date: Thu, 6 Oct 2022 17:07:18 +0200 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 04/07/22 12:49, Laszlo Ersek wrote: > On the NUC, this whole child controller chain, and protocol stack, > breaks down because there is no SerialIo protocol interface in the > protocol db. The following command returns nothing, even after "connect > -r": > >> Shell> dh -d -v -p SerialIo > > (On OVMF, the command returns handle BE, see above.) It's hard to understand the "secret decisions" about physical platform firmware. I'm working with a new NUC now, and this one does provide a functional SerialIo protocol implementation out of the box (with the "AMI Serial I/O Driver" actually doing its job, unlike in the previous NUC). However, TerminalDxe is *still* not included in the platform firmware. Unfathomable. (Well, "TerminalSrc", aka "AMI Terminal Driver" is included, but like on the earlier NUC, it seems to be doing nothing; it doesn't bind SerialIo.) Laszlo