On Sat, Feb 12, 2011 at 01:56:09PM -0500, Andrew Lutomirski wrote: > On Sat, Feb 12, 2011 at 12:55 PM, Guenter Roeck > <guenter.roeck@xxxxxxxxxxxx> wrote: > > On Sat, Feb 12, 2011 at 11:01:11AM -0500, Andrew Lutomirski wrote: > > [ ... ] > > > > Actually, > > > >> fan2_min == 200 (div = 64): > >> fan2_input == 138 (read at a different time, so may differ a little) > >> > >> [56013.556243] Reg 0029 = 99 > >> [56013.556286] Reg 0630 = 0046 > >> [56013.556453] Reg 0658 = 0089 > >> > >> fan2_min == 502 (div = 32): > >> fan2_input == 0 (read at a different time, so may differ a little) > >> > >> [56085.471567] Reg 0029 = 00 > >> [56085.471644] Reg 0632 = 0000 > >> [56085.471804] Reg 0658 = 0000 > > > > Must have been blind. So the RPM register returns 0 as well. Not good. > > Wonder what is going on. > > So far, the highest number I've been able to get out of the counter > register is 0x2e8 by setting div == 16 and playing with the pwm. > > If I set div == 8, then I can't get much above 0x10b. > > I have no idea what's going on either. > Do you always get an output with div==8, or was that at a higher fan speed ? Also, does it ever report 0xff in the 8-bit register, or does it always switch to 0x00 ? > I tried writing 0x80 to 0x508 (which is supposed to turn the whole > thing on), but the only bits that seem to stick are 0x7, so I have no > idea what's going on. > If you set 0x508 to 0, you might see 0xff in the 8-bit register; at least this is what I see. The register seems to be write-only. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
