I want to add XCPM (XNU CPU Power Management support) to self compiled version of the XNU kernels and need people with a properly working development setup. You should start by downloading the following tarballs:
Use Google for further instructions. Feel free to add a link to clear working instructions when you get the job done.
Update
I decided to setup a Github repository for this new project. To make things a tad easier for you. And as a result, you can now download setupXNU.sh and run it. That is all you need to do for now 😉
Pike's Universum 
Hi Pike! Thanks for your terrific work! Does this new project apply to X99 boards patched kernel?
Cris
Perhaps in the future. Not from the start. And I haven’t even committed anything useful. Not to mention that it will take some serious effort (read: time) to complete this project.
Yep, I noticed the new target (X86_64H) since Yosemite.
So it stands for Hasswell… good to know…
Is should be possible to build both kernel at once…
make ARCH_CONFIGS=”X86_64 X86_64H” KERNEL_CONFIGS=RELEASE SDKROOT=/ install
Sure, but XCPM is really more tailored towards Haswell processors. That was why I decided to use it in my script.
I just wanted to mention that the ARCH_CONFIGS=X86_64H builds successfully on my haswell macbook pro. However, just as a test, $sudo nvram boot-args=”kcsuffix=local” (which DOES work on my 2010 non-haswell iMac), doesn’t work. I just end up getting the `forbidden’ symbol upon rebooting. I have to end up using disk utility in recovery mode to “correct things”. What’s up with that ? Is there a different way to install on macbook pros ?
What version of XNU source code are you using?
xnu-2782.1.97
I gotta tell you man, if this is still an xcpm thing, why in the bleep doesn’t apple just publish the source for it! If they don’t, then why don’t they just not publish any of the kernel sources at all anymore. Until this xcpm change happened starting in Mavericks’, I was always able to build xnu kernels. And I’ve been using macs forever! I spend thousands of dollars on “pure” Apple machines man, always have. I really don’t understand what the big deal is about them not wanting to include the xcpm source. If that’s all it would take to avoid these problems. Do you?
Yup. XCPM is not open source, and I don’t expect it to be any time soon. That was why I wanted to share a XCPM library, but received an e-mail threat to stop disassembling their intellectual property or else… and this was one of the reasons for me to step out of the hackintosh scene.
Just out of curiosity, have you ever tried contacting anyone in engineering at Apple, and asking them about this issue involving xcpm?
Have you ever seen any power management source code written by Intel? I’m just saying that it may not be Apple, but Intel who is to blame here. And I did ask questions about it, but nobody wanted to share any information about it. NDA here NDA there. Same crap everywhere.