10:26pendingchaos: imirkin: shouldn't there be a "offset += insn->src(s).get()->reg.data.offset" in TargetNVC0::insnCanLoadOffset() like in TargetNV50::insnCanLoadOffset()?
16:07imirkin: pendingchaos: yep
19:04rhyskidd: what is the best programmatic way in envytools to list all the possible "variants" for rnndb?
19:04rhyskidd: i'm looking to ensure I constrain a mmio range to all pre-Pascal cards
19:06rhyskidd: is it to look at the table in generated cgen/gpu.c?
19:06mwk: yeah, the .c file works just as well
19:08rhyskidd: and is the interval notation [a,c) to indicate an interval from a to c that is inclusive of a but exclusive of c?
19:10rhyskidd: so GF100:GP100 is an interval that is inclusive of Fermi but exclusive of Pascal?
19:10rhyskidd: great, thanks mwk :)
20:07rhyskidd: ^ skeggsb_ you might be interested in the above. nouveau doesn't yet make use of the memory clock command shadow scripts from the vbios that nvgpu uses
20:07rhyskidd: nouveau does use the non-command scripts at the moment
20:11Subv: in envytools, is gf100_m2mf.xml the method layout for engine 0xB0B5 in maxwell?
20:12mwk: that would be gk204_copy.xml
20:13mwk: or something like that
20:13mwk: different engine
20:13mwk: er, gk104_copy.xml
20:56Subv: ah, thanks!
23:07mooch: hey, does anybody know what the different copy modes here do? https://github.com/envytools/envytools/blob/master/rnndb/fifo/gk104_copy.xml#L23
23:08mooch: also, where in nouveau is the copy mode set? i can't even see any code for this object class
23:24mooch: oh, damn, nouveau just uses unk2 all the time
23:32mooch: does anybody know what unk1 and copy mode 3 do?