> Can you try to load wmi.ko with params debug_event=1 and
> debug_dump_wdg=1 if you can see something in dmesg?
I tried that too, to no avail (well, debug_dump_wdg obviously caused the
parsed contents of _WDG to be printed out, but there was only one event
GUID - the one already present in dell-wmi). Even inserting a pr_info()
call at the beginning of acpi_wmi_notify() didn't make a difference.
> Maybe we really need some hack/hook if this is firmware issue...
Probably, but I have no elegant solution (note my lack of kernel and
ACPI expertise, though), only two unholy abominations:
a) install a GPE 0x17 handler which would imitate the actions taken by
the NEVT method and also handle any additional values which may be
returned by ECG1; the 0x0400 branch would come out pretty lengthy,
though,
b) override the ECG1 method (using ACPI method customization) so that
it notifies some otherwise unused ACPI device [1] just before it
returns if an event code not already handled by NEVT is detected;
then implement a standard notify handler for that device; this
requires CONFIG_ACPI_CUSTOM_METHOD or installing a precompiled DSDT
using acpi_install_method(), which would just add to the insanity.
[1] Creating a new one solely for this purpose sounds utterly bonkers.
--
Best regards,
Michał Kępień
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
