| 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: <201103171854.52777.arnd@arndb.de> Date: Thu, 17 Mar 2011 18:54:52 +0100 From: Arnd Bergmann <arnd@...db.de> To: Jonathan Cameron <jic23@....ac.uk> Cc: Kay Sievers <kay.sievers@...y.org>, linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>, Jean Delvare <khali@...ux-fr.org>, Guenter Roeck <guenter.roeck@...csson.com> Subject: Re: IIO comments On Thursday 17 March 2011 17:46:48 Jonathan Cameron wrote: > > > > Since I haven't fully understood the distinction between the > > three chardevs, it may of course turn out a bad idea, but I > > think it would simplify the core code if you could assume > > that every iio device has exactly one chardev interface, > > so you could give them the same unique number and manage > > the life time together. > > It simplifies that corner, but I'm a little worried that it > will add a lot of interlinks between the currently fairly > disconnected elements that go through a character device. > > If we can keep those links to a minimum (which I think > we can, but haven't tried yet!) it will be a sensible move. Let's first work out how a single event buffer should work using read and poll, as discussed in the other thread. Once we have sorted that out, this may become a lot clearer. Arnd -- 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