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.4242.1649318418722620811
 for <devel@edk2.groups.io>;
 Thu, 07 Apr 2022 01:00:19 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hEXk3WP3;
 spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: kraxel@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1649318417;
	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:
	 in-reply-to:in-reply-to:references:references;
	bh=anSrSpZ57OxYfQ3LF5p7sudGDA/6ZTrttK7DFhAz7uY=;
	b=hEXk3WP3rs0fXlVSISdK5QQHbYcd4FMAw1rX212OCwIms31Pd9hbb904VZtd7qKWxtgWVr
	7mxpABmRflzMGvMOcdA8Ve0k/DTyT8xhxW0HjM5b99trRZ7boEim84RCyi0Dnj7AboKHlc
	9dzQTZcntda1br/ULBhXHLH+2Z4MvJg=
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-25-sVwsw_vVO6uBeKC-2arzpQ-1; Thu, 07 Apr 2022 04:00:15 -0400
X-MC-Unique: sVwsw_vVO6uBeKC-2arzpQ-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 7A6EF811E7A;
	Thu,  7 Apr 2022 08:00:15 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.9])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 3638840CFD09;
	Thu,  7 Apr 2022 08:00:15 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 3DD5F18000B3; Thu,  7 Apr 2022 10:00:08 +0200 (CEST)
Date: Thu, 7 Apr 2022 10:00:08 +0200
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: "Ramesh R." <rameshr@ami.com>, Sivaraman Nainar <sivaramann@ami.com>,
	manickavasakam karpagavinayagam <manickavasakamk@ami.com>
Subject: Re: [edk2-devel] Intel NUC platform firmware -- no serial I/O support?
Message-ID: <20220407080008.o2qmtum4sxzw5zfo@sirius.home.kraxel.org>
References: <4c8d982a-97b0-654c-c6db-9a55b95330b5@redhat.com>
MIME-Version: 1.0
In-Reply-To: <4c8d982a-97b0-654c-c6db-9a55b95330b5@redhat.com>
X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

  Hi,

> 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.)

Disclaimer: Havn't used amt/vpro for a quite while.  But possibly those
drivers bind to the serial device which shows up when you enable remote
management and serial-over-lan support?

take care,
  Gerd