From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.61]) by mx.groups.io with SMTP id smtpd.web10.2446.1587374717570351947 for ; Mon, 20 Apr 2020 02:25:18 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=bDPZQV5i; spf=pass (domain: redhat.com, ip: 205.139.110.61, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587374716; 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=eyMRlXVSPHH//aVUGtqgmYFGi0IB7K50J+5BQqoxKek=; b=bDPZQV5iLBrBfLC89OyAh2z8EhEB2OyOxU2qb0LXzSixZakZtOeV0OZrTfEKSMUKVFspjf SSKjEdQ77ENRDHugZNtj4oUeoIxw57YJtNtOcxiJoAG1UH1XcWVuAh2FEMtkP+WK8/WyAi 2A9ue546X1e9XZa3gl46pGUD9V+XhD4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-202-_NybPc0pNC-OPwg_Juy6aA-1; Mon, 20 Apr 2020 05:25:10 -0400 X-MC-Unique: _NybPc0pNC-OPwg_Juy6aA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 519038017F3; Mon, 20 Apr 2020 09:25:09 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-228.ams2.redhat.com [10.36.114.228]) by smtp.corp.redhat.com (Postfix) with ESMTP id B3BF726579; Mon, 20 Apr 2020 09:25:07 +0000 (UTC) Subject: Re: [edk2-devel] [PATCH v1 1/1] NetworkPkg/SnpDxe: Register SnpNotifyExitBootServices at TPL_CALLBACK To: Andrew Fish , devel@edk2.groups.io Cc: "Rabeda, Maciej" , michael.kubacki@outlook.com, Siyuan Fu , Jiaxin Wu , "Tomas Pilar (tpilar)" References: <0CFA9104-ADB5-40F9-B564-A15D76FB58FC@apple.com> From: "Laszlo Ersek" Message-ID: <4e98d616-febc-6f9e-9436-3da184df50b7@redhat.com> Date: Mon, 20 Apr 2020 11:25:06 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <0CFA9104-ADB5-40F9-B564-A15D76FB58FC@apple.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 04/16/20 18:12, Andrew Fish wrote: > Laszlo, > > This is "way back" but UNDI was defined in the Preboot Execution Environment (PXE) Specification. I think version 2.1 was the last one in and it was released in 1999. The how to do it in EFI ended up in the EFI spec. > > PXE was a PC BIOS specification for network booting, UNDI (Universal Network Device Interface) was a standardized abstraction for NIC hardware that goes back to PC BIOS Thanks for the explanation! > The cross link for specs referenced in the UEFI Spec is here: https://uefi.org/uefi. The idea is to keep that up do date. Awesome! I've always missed a page like this! Laszlo