On Fri, 2015-04-03 at 09:55 +0000, Li, Elvin wrote: > Hi Deb and David, > I want to ask this update to CSM 0.98 spec. > CSM 0.98 spec adds 4 new fields. This is my understanding and > question for these new fields after looking at update: > UmaAddress/ UmaSize: The values are assigned by CSM 16. > HiPermanentMemoryAddress/ HiPermanentMemorySize: who will > assign value? CSM16 or CSM32 (LegacyBiosDxe)? If CSM32 assigns, how?
I seem to recall it was assigned by the 32-bit side, to tell the CSM16 where it can make high allocations to avoid fragmenting the high memory map too much. I was going to send that as a second patch after the first one which enabled the UmaAddress/UmaSize feature (which was the most important part). But after waiting this long for the first patch in the series to be applied, I've lost all context. And motivation. Is it actually worth me switching the context back in to sort this out? Will it get applied any time soon? -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
