public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Xu, Min M" <min.m.xu@intel.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	Brijesh Singh <brijesh.singh@amd.com>,
	Erdem Aktas <erdemaktas@google.com>,
	James Bottomley <jejb@linux.ibm.com>,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH V2 0/2] Rename XenTimerDxe to LocalApicTimerDxe
Date: Tue, 2 Nov 2021 10:24:50 +0000	[thread overview]
Message-ID: <PH0PR11MB4885DDADFBE70750600AA2AE8C8B9@PH0PR11MB4885.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211102102100.2k2rplncer3ytprg@sirius.home.kraxel.org>

Usually, we put those information in the header of module INF file.


> -----Original Message-----
> From: Gerd Hoffmann <kraxel@redhat.com>
> Sent: Tuesday, November 2, 2021 6:21 PM
> To: devel@edk2.groups.io; Yao, Jiewen <jiewen.yao@intel.com>
> Cc: Xu, Min M <min.m.xu@intel.com>; Ard Biesheuvel
> <ardb+tianocore@kernel.org>; Justen, Jordan L <jordan.l.justen@intel.com>;
> Brijesh Singh <brijesh.singh@amd.com>; Erdem Aktas
> <erdemaktas@google.com>; James Bottomley <jejb@linux.ibm.com>; Tom
> Lendacky <thomas.lendacky@amd.com>
> Subject: Re: [edk2-devel] [PATCH V2 0/2] Rename XenTimerDxe to
> LocalApicTimerDxe
> 
> On Tue, Nov 02, 2021 at 10:05:56AM +0000, Yao, Jiewen wrote:
> > We can state, this driver is to support fixed frequency.
> > If a real platform happens to have fixed frequency, then it can be used.
> >
> > gEfiMdePkgTokenSpaceGuid.PcdFSBClock  is defined in MdePkg.
> > The consumer need set PcdFSBClock.
> >
> > I don't see a need to bind to OVMF.
> 
> Not needed indeed, but I doubt it'll actually be used outside
> OvmfPkg for the reasons outlined in the last reply.
> 
> When we move it out we should clearly document the PcdFSBClock
> so any potential users are aware of it.  Maybe drop a short
> README into the directory then?
> 
> take care,
>   Gerd


      reply	other threads:[~2021-11-02 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01  8:46 [PATCH V2 0/2] Rename XenTimerDxe to LocalApicTimerDxe Min Xu
2021-11-01  8:46 ` [PATCH V2 1/2] OvmfPkg: " Min Xu
2021-11-01  8:46 ` [PATCH V2 2/2] OvmfPkg: Switch timer in build time for OvmfPkg Min Xu
2021-11-02  9:32 ` [PATCH V2 0/2] Rename XenTimerDxe to LocalApicTimerDxe Gerd Hoffmann
2021-11-02  9:38 ` Yao, Jiewen
2021-11-02  9:58   ` [edk2-devel] " Gerd Hoffmann
2021-11-02 10:05     ` Yao, Jiewen
2021-11-02 10:21       ` Gerd Hoffmann
2021-11-02 10:24         ` Yao, Jiewen [this message]

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=PH0PR11MB4885DDADFBE70750600AA2AE8C8B9@PH0PR11MB4885.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