Hi Hans, > I was thinking about doing things differently with regards to userspace. > As I already posted to the list I'm working on a driver for the uGuru2. > The driver is done (waiting for feedback from testers) but I still need > todo userspace. Since the uGuru2 driver is going to be 2.6 only and > since 2.6 has a clear API/ABI between userspace and the kernel for hwmon > chips I was thinking about adding code to libsensors for generic 2.6 > support. The idea is to write a piece of code which will come into > action only if libsensors doesn't have a chip definition for a found > chip and libsensors is running on a 2.6 kernel. This piece of code > would then fill a dynamicly allocated structure describing the unknown > chip, using the same structure as for known chips. Yes this is in long term plan. > Does this sound like a plan With this in place we no longer need to > write support for every new 2.6 hwmon driver, actually if this goes in I > would like to see explicit support for the uGuru (1) be removed, since > this generic code should do just as good of a job. Yes. There are still questions if to rewrite the libsensors and allow LGPL or change libsensors to what you propose. > Does this sound like a plan (for 2.6 only drivers) ? Or are you > planning on porting this driver to 2.4? No plan for 2.4. I'm leaving now for two weeks so please be patient with further answers from me. Regards Rudolf
