Am 24.06.2016 um 12:20 schrieb Michał Kępień: >> So I got a reply from my vendor CC some Fujitsu persons. >> >> They claim the non-working brightness buttons is an error in an Intel >> driver and they are going to contact the Linux/Ubuntu community. > > I am not sure what the Intel driver has to do with this, but hey, who am > I to tell them how their hardware works? > >> I'll point them to this thread. > > Please do, I will be happy to help. > >> No news yet about the touchpad key. > > Let me think about a patch which would support it. I will get back to > you once I have actual code. There is a key event in input.h called KEY_TOUCHPAD_TOGGLE. Calling the S000 function as call_fext_func(FUNC_RFKILL, 0x0, 0x0, 0x0) should give you the indicator mask call_fext_func(FUNC_RFKILL, 0x1, 0x0, 0x0) should give you the touchpad and brightness indicator and actually reset both indicator states >From the asl, valid first parameters are 0x01 (touch + bright), 0x04 (rfkill) and 0x05 (? something else regarding RF, as it also uses FSMI 0x91) Regards, Jan-Marek P.S. after rebuilding my kernel I can finally build external modules again. Building the deb-pkg target on amd64 for i386 kernel, results in the correct kernel, but amd64-compiled tools needed for modpost. -- 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
