+CC linux-input On 11 July 2011 14:12, Daniel Drake <dsd@xxxxxxxxxx> wrote: > On 11 July 2011 13:18, Karel Zak <kzak@xxxxxxxxxx> wrote:> >>> http://article.gmane.org/gmane.linux.drivers.platform.x86.devel/1089 >> >> Wow, so you have already implemented a patch that exports the state >> in *human readable format* by sysfs. This patch was NACKed. >> >> Now it's expected that everyone in userspace will use ioctl() (with >> root permissions?) and translate any crazy bit array to something >> human readable. Right? Really? > > Dmitry, what are your thoughts on this? > > To clarify, there are 4 different switches that we need to read the state of. > > 1. XO-1.5 lid switch, exposed via ACPI via normal acpi-button driver > 2. XO-1.5 ebook switch, exposed via drivers/platform/x86/xo15-ebook.c > 3. XO-1 lid switch, exposed via arch/x86/platform/olpc/olpc-xo1-sci.c > (linux-next) > 4. XO-1 ebook switch, exposed via > arch/x86/platform/olpc/olpc-xo1-sci.c (linux-next) > > We'd like to do this from shell code, as root. add 2 more to that list as well in the near future: we are currently writing drivers for the lid and ebook switches on the ARM-based XO-1.75 laptop currently in prototype stages. Daniel -- 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
