Messages in this thread | | | Date | Tue, 15 Mar 2005 14:34:07 -0500 (EST) | Subject | Re: [RFC] Changes to the driver model class code. | From | "Sean" <> |
| |
On Tue, March 15, 2005 2:08 pm, Dominik Brodowski said:
> For example, temperature sensors could be exported > using /sys/class/temp_sensors/... -- then userspace wouldn't need to know > whether the temperature was determined using an ACPI BIOS call or by > accessing an i2c device. Such "abstractions", and other kernel code whcih > uses these "abstractions" (a.k.a. class interfaces) are a great feature > to have, and one too less used by now.
That really sounds like a job for user space, why complicate the kernel? A simple user space library could handle returning temperatures without the caller knowing from where the value was obtained. Isn't this the exact type of thing that just bloats a kernel needlessly?
Sean
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |