Hi all: * Jean Delvare <khali at linux-fr.org> [2007-04-11 13:49:01 +0200]: > Hi Hans, > > On Mon, 09 Apr 2007 14:34:35 +0200, Hans de Goede wrote: > > Oh and another thing I just came up with, last time I checked, it isn't > > possible from userspace to change an inX_input to a tempX_input, or are you > > suggesting that I export all 48 sensors, 3 times, once as in, once as temp and > > once as fan and them make user space ignore temp1 and fan1, and use in0, as > > sensor 0/1 actually is an in sensor? > > You're right, this isn't possible, because it's not needed. The drivers > are usually able to read the device configuration from its registers, > and create the right sysfs entries based on that information. The only > exceptions being the vt1211 and gl520sm drivers, which I mentioned in > my previous reply. In this case, there is no practical difference between reading that info from a register on the chip and inferring it from a register on the motherboard. They are a matched pair, indivisible. You can't just buy a tube of uguru3s from digikey and wire them up to random projects like you can w/ e.g. lm93. > So I seem to understand that, for the abituguru3, you are not able to > read the configuration from the device? Again I must blame Abit for > their very poor design and/or lack of documentation :( See above. Lack of docs is bad, of course; but I don't see any problem with that design. It's just different. > Didn't you have the same problem originally in the first abiturugu > driver? If so, how did you solve it? Regards, -- Mark M. Hoffman mhoffman at lightlink.com
