| 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
| ||
|
Date: Thu, 4 Jun 2009 06:06:48 -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:48, David Brownell wrote: > On Thursday 04 June 2009, Mike Frysinger wrote: >> > 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. > > I don't. I see it as an adjunct to real drivers. Or maybe > we just differ on what "simple" means here. > >> 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. > > If that's what you want, why don't you write a custom driver > that provides the kind of command interpreter you want? i had "simple-gpio" but it was rejected as it duplicated too much with the gpio sysfs interface does vectored writes (writve) work with sysfs ? if so, then that should work for back-to-back commands rather than having sysfs do stream parsing. -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