Maybe it's not a quirk after all. acpi_ec.c evaluates "_GPE" and stuffs 
it into sc->sc_gpebit; the comment says that this is the GPE bit (mask? 
bit number?). On my laptop it's being evaluated as 0x1c. sc_gpebit is 
then passed to AcpiClearEvent and AcpiEnableEvent as a message. However, 
the message IDs are hardcoded (not machine dependent) to a range of 
0..4, and don't appear to correspond to interrupt bits. CleanEvent and 
EnableEvent choke on the message id and return error 0x1001 (invalid 
parameter).

 > I tried your patch, and configured in the ec device. It didn't crash
 > anything :) However, it's spitting EC GPE errors every 20 seconds or so:
 >
 > 04:20:41 rex /netbsd: acpiec0: EcRequest: unable to clear EC GPE
 > 04:20:41 rex /netbsd: acpiec0: EcRequest: unable to reenable EC GPE
 > 04:20:41 rex /netbsd: acpiec0: EcRequest: unable to clear EC GPE
 > 04:20:41 rex /netbsd: acpiec0: EcRequest: unable to reenable EC GPE

--
Michael South
msouth@msouth.org