I've recently taken up picking up the Chromebook Pixel off the floor as a brick as I was finally able to replace the stupid BIOS to let me have a decent development OS on it, while grooming the kernel log on firmware_class I see this laptop uses the atmel_mxt_ts touch screen driver and that it looks for the maxtouch.cfg firmware, but doesn't not seem to fail if it doesn't find it. The source code seems to also say: xxd -r -p mXTXXX__APP_VX-X-XX.enc > maxtouch.fw And that Atmel provides such firmwaere in .enc form. Is this firmware optional? If so why? If it gives me a few bells and whistles, what are they ? Can we just put the firmware into the linux-firmware tree? If not, why not. Can the firmware be open sourced? If not why not? [0] Luis [0] Please note, I've heard all excuses about firmware not being opened up, everything is just excuses, I've been able to open source firmware before even for 802.11 devices which are far more complex devices, can someone at Atmel just really try asking? The Chromebook Pixel 2013, given it has no firmware even for 802.11, and you can use coreboot, is likely one of the few devices in the market that you might get without oddball proprietary fuzz. Granted if the firmware is not needed this is moot, but if we can get some enhancements with it and the firmware be opened why not. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
