0000-1248 Posted June 27, 2015 Share Posted June 27, 2015 Hi everyone, I've been involved in the OSx86 project for 3 years now (I'm not a New User but I'm posting here because I don't know where else to put it) and I know all the tools and how to use them, but I want to make my own tools. So what I'm asking is, is the a Beginner's Guide to patching kernels and kexts and learning DSDT code. Please help! As I said, I know all the tools but I want to make my own!! Thanks in advance, -Matt Quote Link to comment Share on other sites More sharing options...
pokenguyen Posted June 27, 2015 Share Posted June 27, 2015 What tools are you mentioning? If you mean Clover, Chameleon, kexts, they are open-source. You should learn C and start reading the source. Quote Link to comment Share on other sites More sharing options...
0000-1248 Posted June 27, 2015 Author Share Posted June 27, 2015 What tools are you mentioning? If you mean Clover, Chameleon, kexts, they are open-source. You should learn C and start reading the source. I would like to learn patching kernels, kexts, DSDTs and Chameleon. If you could reference me a guide that would be great. I have started learning to code in C# if that will be of any use. Thanks in advance, -Matt Quote Link to comment Share on other sites More sharing options...
mendietinha Posted June 27, 2015 Share Posted June 27, 2015 you´ve heard the man. Quote Link to comment Share on other sites More sharing options...
wegface Posted June 27, 2015 Share Posted June 27, 2015 Learn the intel acpi spec, is only 1000 pages. Enjoy. But if true OSx86 died with mavericks (as your sig says) whats the point? Quote Link to comment Share on other sites More sharing options...
mhaeuser Posted June 27, 2015 Share Posted June 27, 2015 There are no guides to patch kernels and kexts because if you are capable of doing so, you don't need a guide. You need at least x86 Assembly Language and C skills, but depending on if you want to do greater patches to kernel or kexts also Objective-C. If you know ASM, I don't think that you still need wide descriptions about what to do. Read up on Reverse Engineering and ASM if you really care. EDIT: C# is barely of use. You learn some vey basic basics, but most of the stuff you will actually need it hidden from you by the language, including pointer work, POD structs, non-OOP patterns and memory management. 2 Quote Link to comment Share on other sites More sharing options...
0000-1248 Posted June 27, 2015 Author Share Posted June 27, 2015 But if true OSx86 died with mavericks (as your sig says) whats the point? I want to use this to code with Mavericks. There are no guides to patch kernels and kexts because if you are capable of doing so, you don't need a guide. You need at least x86 Assembly Language and C skills, but depending on if you want to do greater patches to kernel or kexts also Objective-C. If you know ASM, I don't think that you still need wide descriptions about what to do. Read up on Reverse Engineering and ASM if you really care. EDIT: C# is barely of use. You learn some vey basic basics, but most of the stuff you will actually need it hidden from you by the language, including pointer work, POD structs, non-OOP patterns and memory management. Thanks. I will try to complete these by the end of the year Also I am assuming ASM is the x86 Assembly? Quote Link to comment Share on other sites More sharing options...
mhaeuser Posted June 27, 2015 Share Posted June 27, 2015 Also I am assuming ASM is the x86 Assembly? Correct, it's a frequently used shorten. Good luck. 1 Quote Link to comment Share on other sites More sharing options...
meklort Posted July 7, 2015 Share Posted July 7, 2015 I don't know of any real guide / tutorial that'll help you out.. but there are some pretty good resources. Anyway, I really just want to respond to post a link (cause, awesome link).... For source patches, I suggest you read this. For non-kext based patches, I'd also suggest developing kernel patches using the kext based method in the kernel patcher module... although I'm a little biased (and I don't think anyone had done so yet, although it's *really* easy - no need for assembly) For binary patches, good luck and have fun. There are some techniques that I use, although I haven't written anything up about them. Maybe I will sometime. Until then, It's really your standard debugging techniques that always apply (figure out what works / what doesn't. Figure out where it's broken and how to fix it. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.