| 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: <20090305150334.GC29699@buzzloop.caiaq.de> Date: Thu, 5 Mar 2009 16:03:34 +0100 From: Daniel Mack <daniel@...aq.de> To: linux-kernel@...r.kernel.org Subject: Re: Where to put new sensor drivers? On Sun, Mar 01, 2009 at 01:41:34PM +0100, Daniel Mack wrote: > I wrote a driver for an I2C connected ambient light sensor and submitted > it to the linux-i2c list[1]. In the first place, I wasn't aware of > drivers/i2c/chips being deprecated and hencei, I subsequently moved it to > what seemed to match best in the current tree, drivers/hwmon. But as > Jean Delvare pointed out, this is not the place for it either because it > doesn't really monitor the hardware, which is true. > > So I posted a proposal[2] patch series that adds drivers/sensors for > such cases (some of the drivers in the legacy folder drivers/i2c/chips > have the same problem than my new one has) but haven't got reply on it > yet, probably because linux-i2c is the wrong place to ask. Hmm, no feedback here either? I was pointed to the 'industrial I/O' thread[1], but that one didn't go mainline yet, and I didn't find any reference of someone picking up this idea. Are such drivers not wanted in the kernel? I could also move my code to userspace, but I though if it's supported by the kernel, more people can acutally use it easily. Daniel [1] http://lkml.org/lkml/2008/12/1/156 -- 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