On Sat, 4 Jan 2003, Mark Studebaker wrote: > Couldn't find the thread, but there was some discussion about how > i2c-core returns failures as -1 and the chip drivers just take that, > cast it to a u8, and that gets converted by libsensors and reported as > the value. I think I complained about returning -1 for any errors from i2c-core, even when adapter returned something worth repeating to user, like timeout or hw failure etc. I have not looked if something tests for -1 explicitly, and put some choices in i2c-algo-biths. While the adm change is trivial, it leaves userland with less chance of detecting bus/chip game over situation. The pitfall is that monitoring daemon will choose to draw a straight line and not notify sysadmin nor do any fan(cy) pwm. With /proc there is little to do but give clearly incorrect reading or invent new alarm set if some access failed. Without PEC, bad values come through anyway and need sanity checking for RRD/MRTG/logging. For this type of sysadmin utility, I feel reliability must come first. Whether sensor access over /proc is convenient or (ever) acceptable in Linus's tree is worth considering. Today the choice might be devfs. -- Ky?sti M?lkki kmalkki at cc.hut.fi
