Files
lm-sensors/TODO
T
Frodo Looijaard 45d6e40e75 Example lm_sensors-2 driver
Though it is called the LM78 driver, there is not too much LM78 specific
code in it; it can better be seen as an example code skeleton for other
drivers. Right now, it creats a file /proc/sensors-test, which contains
a list of busses it registered itself on. Stupid, but very useful for
testing purposes!

You need a 2.0 kernel for lm78.o to insert (or hack the /proc system
specific parts; see lm78.c of lm_sensors version 1 how to do this).
Other parts of lm_sensors-2 are not tested for 2.1 kernels either, but
I am certain it won't work in this case :-).

See the TODO list to get some idea what is left to do, choose something
and implement it. Or not :-). But please, send a note to the mailing
list when you start on something, to avoid duplicate work...

Other notable changes:
  the smbus_access routines now use (the more logical) i2c_adapter
  structure, instead of smbus_adapter.


git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@13 7894878c-1315-0410-8ee3-d5d059ff63e0
1998-11-26 10:16:08 +00:00

17 lines
697 B
Plaintext

Many, many things. Most notably:
* Write smbus_access_i2c in smbus.c
* Write piix4_* in piix4.c
* Complete lm78 driver
* Extend dev interface for SMBus
* Create entries in /proc/bus: a list of all registered busses, and for
each bus, a file with registered clients.
* Write all other drivers
* How to make drivers detect thing *not*; for example, if a Winbond is
present, the LM75 driver should not try to access its simulated
LM75 chips!
* Write a userland-library for SMBus/i2c access (through the /dev interface)
* Write a userland detection program for busses (clients are less important;
but perhaps needed too).
* Bring doc/design up-to-date (it is horribly out of date right now)