09:56 qeeg__: imirkin, okay, so RAMHT is at 0, it's 0x4000 long, and yet, the driver is only writing the expected stuff at the 0x7800 range???
11:49 imirkin: qeeg__: so yeah, something in your logic must be off =]
11:50 imirkin: qeeg__: perhaps the ramht size is in bytes while the entry indices are in words/dwords? dunno
13:52 qeeg__: well, the object is at 0x7818, but i'm calculating an address of 0x0018
13:52 qeeg__: and i don't know where that offset is coming from...
19:31 TimurTabi: If I have the driver loaded with modeset=1, is there some command I can send to the driver from the Linux console that will "activate" the driver? For example, with the Nvidia drivers, I could run "nvidia-smi", which will open the driver, trigger loading and initialization of firmware, send some commands to the driver, etc.
19:31 airlied: TimurTabi: the driver is activated if yo loaded it
21:16 karolherbst: TimurTabi: if you want to do acceleration stuff you can also just call glxinfo or just start x
21:16 TimurTabi: I don't want to start any graphics, because I'm not attached via a gui
21:21 karolherbst: why should that be a problem?
21:21 karolherbst: you can just start X or maybe just run kmscube directly on the render node
21:22 karolherbst: of course you can also just write a simple application allocating a channel using nouveaus UAPI, but afaik we don't really have anything like that
21:22 karolherbst: maybe skeggsb has something for testing?
21:23 TimurTabi: I haven't been able to reach him in over a week
21:23 TimurTabi: I was really hoping not write any C code. I don't actually know how to interface to the driver from user space.
21:29 karolherbst: well.. you could also just start X, which should allocate a context automatically
21:31 karolherbst: sometimes you just need to trick X it has a display, but normally it should just work
23:31 imirkin: TimurTabi: if the driver is loaded and bound to the pci device, it is activated.
23:31 imirkin: there are nouveau ioctls you can run on the card node to get more info
23:32 imirkin: this is counter to the nvidia blob driver, which doesn't do anything until you touch something
23:32 imirkin: (except the new kms variant presumably)