Where did the refs.txt come from?

[renordw]

Hey all,

I am not currently actually working on a Hackintosh, but there doesn't seem to be any other community with as much knowledge of the DSDT process as this one, so I hope you guys won't mind answering a question for me.

Currently, I am working on compiling a custom DSDT for Arch Linux, and I see that everywhere there are several refs.txt files floating around. My question is where did these come from, and can I compile my own?

Thank you

 

[RehabMan]

Hey all,

I am not currently actually working on a Hackintosh, but there doesn't seem to be any other community with as much knowledge of the DSDT process as this one, so I hope you guys won't mind answering a question for me.

Currently, I am working on compiling a custom DSDT for Arch Linux, and I see that everywhere there are several refs.txt files floating around. My question is where did these come from, and can I compile my own?

Thank you

refs.txt is for the -fe option (iasl).
It is a plain text file.

 

[renordw]

refs.txt is for the -fe option (iasl).
It is a plain text file.

Thanks, but I guess my question is this: What do they reference? Are the references generic, or do they point to some specific parameters for a particular set of hardware? If there are set-up specific, I would like to generate my own.

 

[RehabMan]

Thanks, but I guess my question is this: What do they reference? Are the references generic, or do they point to some specific parameters for a particular set of hardware? If there are set-up specific, I would like to generate my own.

The content of refs.txt is to account for lack of information in certain AML files.

For the hardware in your profile, you do not likely need refs.txt as your AML bits probably contain embedded External opcodes (which were added in iasl by Intel to address this specific disassembly process).