[edk2] LegacyBios: Update EFI_COMPATIBILITY16_TABLE to match 0.98 CSM spec update

2015-04-03 Thread Li, Elvin
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/

Re: [edk2] LegacyBios: Update EFI_COMPATIBILITY16_TABLE to match 0.98 CSM spec update

2015-04-03 Thread David Woodhouse
On Fri, 2015-04-03 at 09:55 +, 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

[edk2] EDK2: Remove white space in MdePkg/Include/Protocol/GraphicsOutput.h

2015-04-03 Thread Leahy, Leroy P
Attestation: I have made the following change to support Google. Submission: Code clean-up: Remove trailing white space Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Lee Leahy leroy.p.le...@intel.commailto:leroy.p.le...@intel.com GraphicsOutput.h.patch

Re: [edk2] UDK2014.IHV question

2015-04-03 Thread Richardson, Brian
You can compile drivers using the IHV distribution, which is why the BaseTools are included. However, the environment doesn’t include the packages necessary to run NT32 or QEMU environments. You are mixing up the development environment for the driver the environment where you want to run the

Re: [edk2] LegacyBios: Update EFI_COMPATIBILITY16_TABLE to match 0.98 CSM spec update

2015-04-03 Thread Li, Elvin
David, Yes, it is worth! Could you send the full patch now? We could review it now and then check in as long as it is good. Thank you for support. Thanks Elvin -Original Message- From: David Woodhouse [mailto:dw...@infradead.org] Sent: Saturday, April 4, 2015 12:20 AM To: Li,

Re: [edk2] LegacyBios: Update EFI_COMPATIBILITY16_TABLE to match 0.98 CSM spec update

2015-04-03 Thread David Woodhouse
On Sat, 2015-04-04 at 04:29 +, Li, Elvin wrote: David, Yes, it is worth! Could you send the full patch now? We could review it now and then check in as long as it is good. Thank you for support. It's poor engineering practice to make two functional changes within a single patch,

[edk2] PEI memory map and PCI mapping

2015-04-03 Thread Joe Thomas
Folks, I've been tasked with developing a PEI driver for a PCI device. So far, I've managed to enumerate bus 0 -- skipping bridge chips for now but will probably need to support that later -- find the device I'm interested in, and size the memory BAR's. My question is this: