public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"lersek@redhat.com" <lersek@redhat.com>
Cc: "r, ramesh" <rameshr@ami.com>,
	Sivaraman Nainar <sivaramann@ami.com>,
	"KARPAGAVINAYAGAM, MANICKAVASAKAM" <manickavasakamk@ami.com>
Subject: Re: [edk2-devel] Intel NUC platform firmware -- no serial I/O support?
Date: Thu, 7 Apr 2022 22:16:43 +0000	[thread overview]
Message-ID: <MW4PR11MB58214549A267B909D3FF84F3CDE69@MW4PR11MB5821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4c8d982a-97b0-654c-c6db-9a55b95330b5@redhat.com>

Hi Laszlo,

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Laszlo
> Ersek
> Sent: Thursday, April 7, 2022 12:46 AM
> To: edk2-devel-groups-io <devel@edk2.groups.io>
> Cc: r, ramesh <rameshr@ami.com>; Sivaraman Nainar
> <sivaramann@ami.com>; KARPAGAVINAYAGAM, MANICKAVASAKAM
> <manickavasakamk@ami.com>
> Subject: [edk2-devel] Intel NUC platform firmware -- no serial I/O support?
> 
> 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.)

Yeah you are right the Super I/O stuff is barrels of fun. However it is actually a spec defined protocol, it is just in the PI spec not the UEFI spec. The PI spec also counts for addition to MdePkg. On the MinPlatform side we built a small/simple Super I/O bus driver for UARTs and PS/2 keyboard/mouse: https://github.com/tianocore/edk2-platforms/tree/master/Platform/Intel/BoardModulePkg/LegacySioDxe

Volume 5, Chapter 14 of the PI spec waxes rather poetic about how to build a full ISA plug-and-play capable DXE driver stack for a system that incorporates both a Super I/O and physical ISA slots.

I can say is that the NUC team has opted to build their systems with AMI Aptio instead of starting with the Intel reference UEFI firmware. I'm not privy to the conversation there. Accordingly, there might be some Aptio specific drivers as you note in your listing of the driver handle database. I'm afraid I have as much knowledge about how that driver stack works as you do.

Thanks,
Nate
 
> 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
> 
> 
> 
> 
> 


  parent reply	other threads:[~2022-04-07 22:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  7:46 Intel NUC platform firmware -- no serial I/O support? Laszlo Ersek
2022-04-07  8:00 ` [edk2-devel] " Gerd Hoffmann
2022-04-07 10:49   ` Laszlo Ersek
2022-04-07 12:50     ` Gerd Hoffmann
2022-04-07 14:12       ` Laszlo Ersek
2022-04-07 17:04         ` manickavasakam karpagavinayagam
2022-04-08  9:19           ` Laszlo Ersek
2022-04-12 18:40             ` manickavasakam karpagavinayagam
2022-04-13  6:06               ` Laszlo Ersek
2022-04-08  9:48         ` Gerd Hoffmann
2022-04-08 11:01           ` Laszlo Ersek
2022-10-06 15:07     ` Laszlo Ersek
2022-04-07 22:16 ` Nate DeSimone [this message]
2022-04-08  9:32   ` Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MW4PR11MB58214549A267B909D3FF84F3CDE69@MW4PR11MB5821.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox