On Sun, 2008-09-21 at 23:17 +0400, Alexey Starikovskiy wrote:
The issue on Asus-EEEPC of bug11089 is that EC notification event is
triggered too quickly. Before the EC notification event is queried,
another EC notification event is triggered again. In such case some EC
notification event will be lost unless EC driver continues to query the
EC notification event until zero is returned. (As suggested in the
Alan's patch).
And it is different with the issue of bug 9998/10724.
> Regards,
> Alex.
>
>
> Alan Jenkins wrote:
> > Alexey Starikovskiy wrote:
> >
> >> Here is the patch.
> >>
> >> Please try/review.
> >>
> >> Regards,
> >> Alex.
> >> Alan Jenkins wrote:
> >>> Sounds sensible. Hopefully we're right that most systems with these
> >>> broken EC's don't want the workaround. I assume you will still notify
> >>> the user automatically, something like "acpi: ec: GPE storm detected,
> >>> try booting with ec=poll".
> >
> > My apologies. I seem to have tested this but neglected to reply :-(.
> >
> > I've been running with this for a week or so now. I've been bashing the
> > hotkeys (and holding down the ones with autorepeat), and it works fine.
> > Plus I get the message in the kernel log suggesting ec_intr=0 if the
> > keyboard doesn't work. It's all good.
> >
> > Thanks
> > Alan
>
> --
> 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
--
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
