From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "MohammadYounasKhan.P@Dell.com" <MohammadYounasKhan.P@Dell.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Question regarding CMOS regions.
Date: Thu, 16 Aug 2018 06:08:15 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BDD7A02@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <c94145c3fc87468586e507a51436fdd6@BLRX13MDC420.AMER.DELL.COM>
Younas,
Why are you still working on CMOS in now UEFI world?
Detailed answer is in below.
Thanks/Ray
> -----Original Message-----
> From: edk2-devel <edk2-devel-bounces@lists.01.org> 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.
>
> Hi Guys,
>
> Please help to reply to my below queries.
>
> Thank you,
> Younas.
>
> -----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.
>
> Hi All,
>
> 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 using IO
> ports 0x72-0x73.
>
> 1. How to know that the system has 128bytes of CMOS or 256 bytes of CMOS
> 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 exists or
> valid or any other mechanism for it?
Refer to #1.
> 3. Are we replicating lower 128 bytes to upper 128 bytes in CMOS location
> 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.
>
> 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
next prev parent reply other threads:[~2018-08-16 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e3e92eaef855481ea1183207018fcc47@BLRX13MDC424.AMER.DELL.COM>
[not found] ` <1b14d8bcb83c4db48a7f4b72f8b8dff6@BLRX13MDC420.AMER.DELL.COM>
[not found] ` <cb259067389a48d88bac493203f1c71d@BLRX13MDC420.AMER.DELL.COM>
2018-08-14 3:47 ` FW: Question regarding CMOS regions MohammadYounasKhan.P
2018-08-16 4:44 ` MohammadYounasKhan.P
2018-08-16 6:08 ` Ni, Ruiyu [this message]
2018-08-16 6:28 ` MohammadYounasKhan.P
2018-08-16 6:59 ` Ramesh R.
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=734D49CCEBEEF84792F5B80ED585239D5BDD7A02@SHSMSX104.ccr.corp.intel.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