Okay, I think I might have a bit of a problem of understanding here. If
rivatuner.exe /i2cd
gives me this:
andCode:Scanning I2C bus 0... Probing device 00... Invalid device [snip] Probing device 4f... Invalid device Scanning I2C bus 1... Probing device 00... Invalid device [snip] Probing device 37... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Probing device 38... Invalid device [snip] Probing device 4f... Invalid device Scanning I2C bus 2... Probing device 00... Invalid device [snip] Probing device 4f... Invalid device Scanning I2C bus 3... Probing device 00... Invalid device [snip] Probing device 0c... 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D 5D Probing device 0d... Invalid device [snip] Probing device 2e... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF BC 00 00 85 81 85 96 10 FF FF FF FF FF FF 80 FF 00 9A 62 A4 20 00 FF FF FF 00 00 73 41 69 45 E0 10 1F 00 FF 00 FF 00 FF 00 FF 00 FF 81 9F 54 7C 90 A9 FF FF FF FF 00 80 FF FF 02 60 80 C8 CC CC 20 00 68 80 80 81 64 9A A1 A4 AB 01 40 00 00 00 00 00 CF FF 2C CC 1A 00 00 57 30 01 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Probing device 2f... Invalid device [snip]
rivatuner.exe /ri<I2C_bus>,<I2C_device>,<reg>
is reading out a devices register located on one of 4 i2c buses, then why am I able to read out my VRM's 3D mode voltage register value with
RivaTuner.exe /sd0 /ri3,70,18 ?
If I understand this right I'm addressing device 70 on the 3rd bus from the first card, while that i2c scan dump oviously gives me 0c and 2e on bus 3? I found out that 18 contains my 3D VID with the help of this thread, what I'm not getting is that why the device addresses are not matching, but the whole command still works? What am I missing?
Reply With Quote
Bookmarks