| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <8bd0f97a0906040220k6f56b944n733a2b3469faaccb@mail.gmail.com> Date: Thu, 4 Jun 2009 05:20:30 -0400 From: Mike Frysinger <vapier.adi@...il.com> To: David Brownell <david-b@...bell.net> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] gpio sysfs: add a "toggle" value On Thu, Jun 4, 2009 at 05:15, David Brownell wrote: > On Thursday 04 June 2009, Mike Frysinger wrote: >> the point was to lower the number of user<->kernel transitions. yes, >> all of this stuff can of course be done in the shell, but it's hard to >> push limits when the interface is tying your hands and sitting on your >> back. > > So what's the application that needs to do all this in > userspace yet which can't hook up a quick kernel driver? > > I don't like the idea of embedding any kind of interpreter > in the sysfs interface, but that's the direction you seem > to be heading ... i dont view the userspace GPIO interface as a simple "i want to wiggle pins for fun and testing". i see it as a dynamic method for building userspace drivers for simple devices. as such, having a very simple "command language" for optimizing the interaction provides a pretty good trade off between kernel complexity and lowering overhead imo. -mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists