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.133.124])
 by mx.groups.io with SMTP id smtpd.web12.3954.1649317583914659382
 for <devel@edk2.groups.io>;
 Thu, 07 Apr 2022 00:46:24 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=X32oML3C;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1649317583;
	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;
	bh=9gtW7rJg9WII1GCmQmqpYl8qMZE2BVRv8YAvmxcssZY=;
	b=X32oML3CsH/Cz3gbmFW4JobFSxWrUwvMdpWXiK581AVlqxNGTQ5l+12lvaoODZRqKO48K8
	ljtBjNXbP1jb+IW7aVrMIuno0rUMOrU2qMnhEuhFg4q3ng9awFbVvDel9aBHNdPgsZh5H+
	pNZXjdMo9C1y8j8IFDxQUbgJZiHgeQE=
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-62-WXxVgRtVMFC8gl8KZIYV2A-1; Thu, 07 Apr 2022 03:46:15 -0400
X-MC-Unique: WXxVgRtVMFC8gl8KZIYV2A-1
Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 9FEBE811E80;
	Thu,  7 Apr 2022 07:46:14 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (unknown [10.39.192.23])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id C42D242D3C6;
	Thu,  7 Apr 2022 07:46:13 +0000 (UTC)
To: edk2-devel-groups-io <devel@edk2.groups.io>
From: "Laszlo Ersek" <lersek@redhat.com>
Subject: Intel NUC platform firmware -- no serial I/O support?
Cc: "Ramesh R." <rameshr@ami.com>, Sivaraman Nainar <sivaramann@ami.com>,
 manickavasakam karpagavinayagam <manickavasakamk@ami.com>
Message-ID: <4c8d982a-97b0-654c-c6db-9a55b95330b5@redhat.com>
Date: Thu, 7 Apr 2022 09:46:12 +0200
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.9
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com
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

Hi List,

my toolbox has been extended with an Intel NUC, the base kit model being
NUC8i3PNH. The NUC has a serial port connector on the back, and indeed
Serial I/O works fine once an OS starts.

However, the UEFI platform firmware seems to have no support for Serial
I/O. I've built a fresh UEFI Shell binary from edk2 master and poked
around in the protocol database, with "drivers" and "dh". The necessary
drivers seem to be included, however they do not appear to bind the
hardware that's inside the chassis. ("connect -r" makes no difference in
this regard, so it's not just BDS policy.)

Interestingly, the related drivers are all called "AMI ...", which I
find somewhat strange on an Intel-branded NUC. I don't know whom I
should be addressing with my question in the first place. Just to be
sure, I'm CC'ing a bunch of randomly picked @ami.com email addresses
from my edk2-devel list archive.

I can provide more details if needed, but first I'd like to ask if *any*
firmware update exists for this kit -- NUC8i3PNH -- where the platform
firmware can drive the serial port. My goal is (of course) completely
headless operation of the NUC; ideally, that would cover the UEFI
console too.

Right now, I need to connect an HDMI monitor and a USB keyboard+mouse to
the NUC just to get into the Setup UI / UEFI Shell.

Thanks!
Laszlo