From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.31; helo=mga06.intel.com; envelope-from=ruiyu.ni@intel.com; receiver=edk2-devel@lists.01.org Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id E8FB221B02822 for ; Wed, 15 Aug 2018 23:08:28 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Aug 2018 23:08:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.53,246,1531810800"; d="scan'208";a="73108590" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by FMSMGA003.fm.intel.com with ESMTP; 15 Aug 2018 23:08:21 -0700 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 15 Aug 2018 23:08:21 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by fmsmsx116.amr.corp.intel.com (10.18.116.20) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 15 Aug 2018 23:08:21 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.143]) by shsmsx102.ccr.corp.intel.com ([169.254.2.226]) with mapi id 14.03.0319.002; Thu, 16 Aug 2018 14:08:15 +0800 From: "Ni, Ruiyu" To: "MohammadYounasKhan.P@Dell.com" , "edk2-devel@lists.01.org" Thread-Topic: Question regarding CMOS regions. Thread-Index: AdQwbXw0bU09G6E1SGqYwJK+xDH0yQCldFkAAABUloAAHxeNsABmsI1QAALlTaA= Date: Thu, 16 Aug 2018 06:08:15 +0000 Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BDD7A02@SHSMSX104.ccr.corp.intel.com> References: <1b14d8bcb83c4db48a7f4b72f8b8dff6@BLRX13MDC420.AMER.DELL.COM> <2d9aeae9d4c94b2c9c1f63161b94c9f5@BLRX13MDC420.AMER.DELL.COM> In-Reply-To: Accept-Language: en-US, zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: Question regarding CMOS regions. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 06:08:29 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Younas, Why are you still working on CMOS in now UEFI world? Detailed answer is in below. Thanks/Ray > -----Original Message----- > From: edk2-devel On Behalf Of > MohammadYounasKhan.P@Dell.com > Sent: Thursday, August 16, 2018 12:44 PM > To: edk2-devel@lists.01.org > Subject: Re: [edk2] Question regarding CMOS regions. >=20 > Hi Guys, >=20 > Please help to reply to my below queries. >=20 > Thank you, > Younas. >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Pathan, MohammadYounasKhan > Sent: Tuesday, August 14, 2018 9:17 AM > To: edk2-devel@lists.01.org > Subject: [edk2] FW: Question regarding CMOS regions. >=20 > Hi All, >=20 > As we know CMOS data can be 128 or 256 bytes. CMOS lower 128 bytes are > stored in IO ports 0x70-0x71 whereas CMOS upper 128 bytes are stored usin= g IO > ports 0x72-0x73. >=20 > 1. How to know that the system has 128bytes of CMOS or 256 bytes of CM= OS > region? You could read the data to know whether high 128 bytes are valid or not. > 2. Is there any CMOS location which represents CMOS upper region is ex= ists or > valid or any other mechanism for it? Refer to #1. > 3. Are we replicating lower 128 bytes to upper 128 bytes in CMOS locat= ion > 0x70-0x71 (or 0x72-0x73)? If yes, Why are we doing that? It depends on BIOS implementation. I don't see any bios is duplicating the = contents. >=20 > Thank you, > Younas. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel