- Joined
- May 2, 2020
- Messages
- 228
Ever since I started this little hobby, first step was to fire-up SSDTTime, generate HPET one and dutifully add it to my EFI. But I wonder — how can I really tell I need it?
I tested my build without it (and related patches) and audio through back I/O headphone jack works.
DSDT has this for HPET:
and this is what SSDT-Time generated:
Apart from Interupt 11, looks pretty much the same.
What would be the tell-tale sign in DSDT that one needs custom SSDT-HPET?
I tested my build without it (and related patches) and audio through back I/O headphone jack works.
DSDT has this for HPET:
Code:
Device (HPET)
{
...
Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
{
Name (BUF0, ResourceTemplate ()
{
IRQNoFlags ()
{0}
IRQNoFlags ()
{8}
Memory32Fixed (ReadOnly,
0xFED00000, // Address Base
0x00000400, // Address Length
)
})
Return (BUF0) /* \HPET._CRS.BUF0 */
}
}
and this is what SSDT-Time generated:
Code:
DefinitionBlock ("", "SSDT", 2, "CORP", "HPET", 0x00000000)
{
External (HPET, DeviceObj)
Name (\HPET._CRS, ResourceTemplate () // _CRS: Current Resource Settings
{
IRQNoFlags ()
{0,8,11}
Memory32Fixed (ReadWrite,
0xFED00000, // Address Base
0x00000400, // Address Length
)
})
}
Apart from Interupt 11, looks pretty much the same.
What would be the tell-tale sign in DSDT that one needs custom SSDT-HPET?