Do we have any time estimates from Elan about when this firmware will land?

Unfortunately not really.

We've finished all the reverts, so the devices in question are in a semi-good state now.  (Before the reverts some of their touchpads simply stopped working entirely)

We have to wait for Elan to provide up new firmwares that fix this issue before we can upload them, and I haven't heard an eta from them yet.  I wouldn't expect it to take overly long though -- a few weeks maybe?

Do we have any updates from Elan?

They are waiting on hardware to test :/ I'll add you to the thread

Removing stable release block label as we reverted failing firmware and are waiting for Elan. I think it's safe to patch this in stable once Elan get back to us.

Elan has let us know that verification of new firmware is almost complete on their end.  We should get the updated firmware this week.  Given the low frequency occurrence of both issues, we'll need to reach out to users on beta channel to be sure there are no further problems.

Does M-54 sound like a reasonable target to everyone else?  We're almost to branch point, but if we see any problems we can revert and go for M-55.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-swanky-private/+/0166b8c66680f3b519257a23a039d901a933fa57

commit 0166b8c66680f3b519257a23a039d901a933fa57
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Fri Aug 19 20:46:47 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-swanky-private/+/0166b8c66680f3b519257a23a039d901a933fa57

commit 0166b8c66680f3b519257a23a039d901a933fa57
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Fri Aug 19 20:46:47 2016

I just merged the new FW for Swanky into ToT (FW version 5.0) so Swanky should be up to date in version >= M54

Patched:
 - Swanky  >= M54
 - Blaze   >= M51

Unpatched:
 - Gnawty
 - Big
 - Kip
 - Kip14

Attaching the latest FWs submitted my Elan for record-keeping
  - Gnawty: 12.0
  - Big: 11.0
  - Blaze/Kip14: 3.0

Note: Kip is missing, we're currently working on figuring out Kip's status with Elan.

Also note: Kip14 and Blaze have the same touchpad HW, so the FW for Blaze works with Kip14 as well.  Currently it is only merged into the tree for Kip14 though.

Deleted: gnawty_12.0.bin 48.0 KB

gnawty_12.0.bin 48.0 KB Download

Deleted: big_11.0.bin 48.0 KB

big_11.0.bin 48.0 KB Download

Deleted: blaze_kip14_3.0.bin 48.0 KB

blaze_kip14_3.0.bin 48.0 KB Download

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-kip-private/+/c81b56a8808752eaae7bf3a55b6cfbf56afa691b

commit c81b56a8808752eaae7bf3a55b6cfbf56afa691b
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Wed Aug 24 22:35:25 2016

The commit in comment #12 uploaded the new touchpad FW for Kip14.  This means the current state for the effected machines is:

Patched:
 - Swanky Version 5.0 fixed in >= M54
 - Kip14  Version 3.0 fixed in >= M54
 - Blaze  Version 3.0 fixed in >= M51

Unpatched:
 - Gnawty
 - Big
 - Kip

We have FWs for the remaining 3 systems, and will merge them after the 54 branch to spread out the rollout to prevent having to mass revert again if they all hit stable at the same time and have another isssue

I have patches in review now to merge in the new firmwares for Gnawty and Big.  Once they're reviewed and merged into ToT, the system should post on this bug.

Regarding Kip -- After offline discussions with Elan, we're told that Kip's touchpad is not actually effected by this bug.  However, there are problems with the field for Kip's touchpad all the same, so I'm breaking Kip off into its own bug on the partner tracker so we can discuss it with Elan there and hopefully find a solution sooner rather than later.  The link (sorry, but it's accessible by ChromeOS partners only) for the new, Kip bug is here:
https://code.google.com/p/chrome-os-partner/issues/detail?id=57508

----------------


Patched:
 - Swanky Version 5.0 fixed in >= M54
 - Kip14  Version 3.0 fixed in >= M54
 - Blaze  Version 3.0 fixed in >= M51

CLs in review now:
 - Gnawty
 - Big

Moved to new bug, will track this elsewhere:
 - Kip

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-variant-nyan-big-private/+/1c7c9a8832c9e4bfa106ba2684c8471ef25213ed

commit 1c7c9a8832c9e4bfa106ba2684c8471ef25213ed
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Tue Sep 13 18:17:52 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-variant-nyan-big-private/+/1c7c9a8832c9e4bfa106ba2684c8471ef25213ed

commit 1c7c9a8832c9e4bfa106ba2684c8471ef25213ed
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Tue Sep 13 18:17:52 2016

That patch (double posted for some reason, but it's just one CL) brought Big up to FW version 11.0

Patched:
 - Swanky Version 5.0  fixed in >= M54
 - Kip14  Version 3.0  fixed in >= M54
 - Blaze  Version 3.0  fixed in >= M51
 - Big    Version 11.0 fixed in >= M55

CLs in review now:
 - Gnawty

Moved to new bug, will track this elsewhere:
 - Kip

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-gnawty-private/+/4cd55f9ef6dd56059ddd3e378e52e00124a7527c

commit 4cd55f9ef6dd56059ddd3e378e52e00124a7527c
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Tue Sep 13 19:24:29 2016

Allright, everything but Kip is merged into various branches that will gradually roll out to users now.  Kip is being investigated aggressively as we speak.

Patched:
 - Swanky Version 5.0  fixed in >= M54
 - Kip14  Version 3.0  fixed in >= M54
 - Blaze  Version 3.0  fixed in >= M51
 - Big    Version 11.0 fixed in >= M55
 - Gnawty Version 12.0 fixed in >= M55

Moved to new bug, will track this elsewhere:
 - Kip  (https://code.google.com/p/chrome-os-partner/issues/detail?id=57508)

verified on M54 and M55 builds