On 4/1/07, koko <citizenr@xxxxxxxxx> wrote:
>blabal
hmmm
Mux 0 Asus IO mux, IO 0000e44dh, Ext 4267320
rasz@capek:~$ cat /proc/ioports|grep e4
e400-e47f : motherboard
e400-e403 : ACPI PM1a_EVT_BLK
e404-e405 : ACPI PM1a_CNT_BLK
e408-e40b : ACPI PM_TMR
e410-e415 : ACPI CPU throttle
e420-e423 : ACPI GPE0_BLK
I decompiled ACPI DSDT from my bios and found this :
OperationRegion (\SGPO, SystemIO, 0xE44C, 0x04)
Field (SGPO, ByteAcc, NoLock, Preserve)
{
GPO0, 1,
Offset (0x01),
GPO8, 1,
, 2,
GP11, 1,
Offset (0x04)
}
1 is my ACPI broken? it doesnt claim 0xe44d as motherboard resource?
Or is Kernel ACPI handling broken? there are other e4xx regions in my
DSDT that are not claimed.
OperationRegion (GPOB, SystemIO, 0xE42A, 0x02)
OperationRegion (GPSC, SystemIO, 0xE42F, 0x01)
2 which bits exactly should I fiddle with? and how, is there a simple
way to play with them (like isaset/isadump for ports)?
3 Is work on i2c-virtual desired? or is this idea abandoned completely
by now and I should write a hack just for me?
--
Who logs in to gdm? Not I, said the duck.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
