- Joined
- Feb 18, 2011
- Messages
- 17
- Motherboard
- OS X 10.9
- CPU
- Intel Z97 LGA 1150/ i7 4790k
- Graphics
- PNY GTX 770
- Mac
- Classic Mac
- Mobile Phone
Hi. I know next to nothing about hardware, but I'm coming up on my third Hackintosh (I've been using nothing but for... 5 or 6 years). Every time I try to get a little more competent at the process.
I write Python, PHP, Javascript, etc. (web developer ftw); so the editing part doesn't alarm me, I can pick up syntax in a jif. But I don't have the slightest clue about what sort of edits to make, why I should or should not make them, etc.. Semantically, a DSDT file is utterly opaque to me.
I'm sure this is a frequent question, but googling it really hasn't proved productive, mostly I find variations on how to open the file and make edits, not how to become informed about editing.
Can someone point me to resources? Or explain what knowledge(s) is/are involved in becoming DSDT savvy? When I write code for myself or a client, I am able to evaluate whether it's stupid code, whether it could be better, what appropriate values are, etc.—how do I gain this level of competence with DSDT editing? Or, if I don't, how do I know I don't? The idea of copying and pasting values from *any* resource and then applying them directly to my rig without being able to evaluate the quality thereof, to me, is just alarming and kind of stupid. But lots of people seem very confident about just slapping up a DSDT they find on the web. Where is this confidence coming from, what am I missing?
I write Python, PHP, Javascript, etc. (web developer ftw); so the editing part doesn't alarm me, I can pick up syntax in a jif. But I don't have the slightest clue about what sort of edits to make, why I should or should not make them, etc.. Semantically, a DSDT file is utterly opaque to me.
I'm sure this is a frequent question, but googling it really hasn't proved productive, mostly I find variations on how to open the file and make edits, not how to become informed about editing.
Can someone point me to resources? Or explain what knowledge(s) is/are involved in becoming DSDT savvy? When I write code for myself or a client, I am able to evaluate whether it's stupid code, whether it could be better, what appropriate values are, etc.—how do I gain this level of competence with DSDT editing? Or, if I don't, how do I know I don't? The idea of copying and pasting values from *any* resource and then applying them directly to my rig without being able to evaluate the quality thereof, to me, is just alarming and kind of stupid. But lots of people seem very confident about just slapping up a DSDT they find on the web. Where is this confidence coming from, what am I missing?