NetBSD Problem Report #57428

From www@netbsd.org  Mon May 22 16:17:36 2023
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 9DBA01A923A
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 22 May 2023 16:17:36 +0000 (UTC)
Message-Id: <20230522161735.6EA4B1A9241@mollari.NetBSD.org>
Date: Mon, 22 May 2023 16:17:35 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: x86 should be able to use EFI RTC automagically
X-Send-Pr-Version: www-1.0

>Number:         57428
>Category:       port-amd64
>Synopsis:       x86 should be able to use EFI RTC automagically
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-amd64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 22 16:20:00 +0000 2023
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The NetBSD Efibootdation
>Environment:
>Description:
As far as I can tell, on x86, NetBSD doesn't ever set or examine the EFI real-time clock with EFI runtime services.  It probably should.
>How-To-Repeat:
code inspection
>Fix:
Yes, please!

Home	PR Database Search