Re: [PATCH v3 12/17] x86: Return mtrr_add_request() to its old purpose

Hi Simon, On Tue, May 9, 2023 at 11:08 AM Simon Glass wrote: > > Hi Bin, > > On Mon, 8 May 2023 at 08:51, Bin Meng wrote: > > > > On Mon, May 8, 2023 at 10:48 PM Bin Meng wrote: > > > > > > Hi Simon, > > > > > > On Fri, May 5, 2023 at 6:51 AM Simon Glass wrote: > > > > > > > > This function us

Re: [PATCH v3 12/17] x86: Return mtrr_add_request() to its old purpose

Hi Bin, On Mon, 8 May 2023 at 08:51, Bin Meng wrote: > > On Mon, May 8, 2023 at 10:48 PM Bin Meng wrote: > > > > Hi Simon, > > > > On Fri, May 5, 2023 at 6:51 AM Simon Glass wrote: > > > > > > This function used to be for adding a list of requests to be actioned on > > > relocation. Revert it b

Re: [PATCH v3 12/17] x86: Return mtrr_add_request() to its old purpose

On Mon, May 8, 2023 at 10:48 PM Bin Meng wrote: > > Hi Simon, > > On Fri, May 5, 2023 at 6:51 AM Simon Glass wrote: > > > > This function used to be for adding a list of requests to be actioned on > > relocation. Revert it back to this purpose, to avoid problems with boards > > which need control

Re: [PATCH v3 12/17] x86: Return mtrr_add_request() to its old purpose

Hi Simon, On Fri, May 5, 2023 at 6:51 AM Simon Glass wrote: > > This function used to be for adding a list of requests to be actioned on > relocation. Revert it back to this purpose, to avoid problems with boards > which need control of their MTRRs (i.e. those which don't use FSP). > > The mtrr_s

[PATCH v3 12/17] x86: Return mtrr_add_request() to its old purpose

This function used to be for adding a list of requests to be actioned on relocation. Revert it back to this purpose, to avoid problems with boards which need control of their MTRRs (i.e. those which don't use FSP). The mtrr_set_next_var() function is available when the next free variable-MTRR must