On Tue, 9 Apr 2019 23:25:25 +0200 Fil <[email protected]> wrote:
> It's also relevant for I9100, if I recall correctly.. I've tested the i9100 and everything looks fine. Galaxy S 2 (I9100): ------------------- Kernel configuration: > # CONFIG_KEYBOARD_CYPRESS_TOUCH is not set > CONFIG_KEYBOARD_CYPRESS_TOUCH_BLN=y > CONFIG_TOUCHKEY_BLN=y Test results: - The touchkey work fine and illuminate when needed both in the recovery and in the regular distribution. - No reboot are seen after more than one leaving the device unattended and unplugged. Galaxy S 3 4G (I9305): ---------------------- Kernel configuration: > CONFIG_KEYBOARD_CYPRESS_TOUCH=y > # CONFIG_KEYBOARD_CYPRESS_TOUCH_BLN is not set Test results: - Reboots with the stock Replicant 6.0 0003 as well as the images I built for testing the touchkey. I don't know if it's related to my device somehow or the images. Do other people have the same behavior with the stock Replicant 0003 images? The Galaxy S 3 (I9300), Galaxy Note (N7000) and Galaxy Note 2 (N7100) uses the following kernel configuration, so they need to be tested as well: > CONFIG_KEYBOARD_CYPRESS_TOUCH=y > # CONFIG_KEYBOARD_CYPRESS_TOUCH_BLN is not set The Galaxy Note 8.0 (N5100) and the Galaxy Note 8.0 (N5110) also use the same kernel but they have the following kernel configuration: > # CONFIG_KEYBOARD_CYPRESS_TOUCH is not set > # CONFIG_KEYBOARD_CYPRESS_TOUCH_BLN is not set so they should not be affected by that set of changes. As for the other devices supported use a different without that touchkey driver. Denis.
pgplHVR3Xtadm.pgp
Description: OpenPGP digital signature
_______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
