| 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: Wed, 2 Aug 2006 21:51:07 +0200 From: Pavel Machek <pavel@...e.cz> To: Jean Delvare <khali@...ux-fr.org> Cc: Greg KH <greg@...ah.com>, lm-sensors@...sensors.org, Shem Multinymous <multinymous@...il.com>, "Brown, Len" <len.brown@...el.com>, Matthew Garrett <mjg59@...f.ucam.org>, vojtech@...e.cz, kernel list <linux-kernel@...r.kernel.org>, linux-thinkpad@...ux-thinkpad.org, linux-acpi@...r.kernel.org Subject: Re: Generic battery interface Hi! > > Actually I do not see "hwmon infrastructure" to exist. Every driver > > just uses sysfs directly. I'm not sure that the best option -- > > "input-like" infrastructure can make drivers even shorter -- but > > perhaps just directly using sysfs is best for simple task like a battery? > > > > Jean, any ideas? > > I guess we never felt any need for an "infrastructure", else we would > have created it. I have no idea what the "input infrastructure" looks > like so I can't compare. If you have something to propose which would > refactor some code amongst the hardware monitoring drivers or would > otherwise makes thing better, speak up :) I'm not sure if it is practical for hwmon, but having report_voltage(x,y) is probably easier than coding sysfs stuff by hand. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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