RageLtMan d02624bbaf valid_mmap_phys_addr_range conflicts with upstream ...

PaX implements valid_mmap_phys_addr_range in the kernel, and the
(return 1) hack in chipsec_km.c has a name collision with it.

Add another conditional for exposing the definition predicated on
whether __HAVE_ARCH_PAX_OPEN_USERLAND is defined in the kernel
headers. If it is, dont redefine the original function.

2019-11-06 20:26:22 -08:00

..

linux

valid_mmap_phys_addr_range conflicts with upstream

2019-11-06 20:26:22 -08:00

osx

Expand OSX driver functionality

2017-10-23 08:34:33 -07:00

win7

Added build notes based upon compilation feedback

2019-08-19 13:06:47 -07:00