00:14 skeggsb: gnurou: i had a script that pulled all the netlists out of the binary driver actually, register ranges for each block were derived from scans/rnndb/gk20a (and are probably not quite right in some cases)
00:15 skeggsb: it pulled it all together, and compared/squashed the sequences down into the format they exist in the driver now
00:15 skeggsb: don't have the script anymore because we can't find the netlist images in the binary driver blob anymore for some reason...
00:15 skeggsb: i've got wip to add the gm204 ones, but haven't pushed them yet because, well, they're useless with the stupid firmware situation..
00:16 skeggsb: wip patches*
00:26 gnurou: right
00:26 gnurou: clever using the netlists to get the register ranges
00:26 skeggsb: it was more straightforward than ripping the same data out of traces :)
00:27 gnurou: I might currently be doing the same thing for GM20B actually
00:27 skeggsb: yeah, i figured that's why you were asking :)
00:28 skeggsb: if you guys are planning on releasing the netlists (assuming they're still used?) along with the firmware, i'd not even be opposed to switching to using those directly
00:28 gnurou: actually I was about to ask whether that would be acceptable
00:28 skeggsb: our ucode operates a bit differently to yours in that the host uploads the register lists manually, rather than being hardcoded in the ucode
00:29 skeggsb: but.. if *all* our supported chipsets use the same method, i have no opposition
00:29 skeggsb: i'd rather not special-case gk20a just because...
00:29 skeggsb: err. gk208/gm20b
00:29 skeggsb: 20a*
00:29 gnurou: well we might want to do the same for GK20A eventually
00:30 skeggsb: yeah. i just don't want big differences between "chipsets nvidia want to officially support" vs the stuff we reverse engineer
00:30 gnurou: it happens to work with the gk104 packs, but there might still be issues that will arise because something is not initialized as it should
00:30 gnurou: sure, I am keeping that in mind
00:30 skeggsb: yeah, i wondered about that when you committed the initial support
00:30 skeggsb: it seemed like there should've been some specifics that were missed
00:31 gnurou: with more experience today I would be surprised if there wasn't :)
00:31 gnurou: re: firmwares, actually I am waiting for the last IP clearance to submit the FECS/GPCCS FWs for GK20A
00:32 skeggsb:is far more interested in PMU for GM204 :P
00:32 gnurou: we will be doing it nouveau-style, e.g. nvea_fucxxxx
00:32 skeggsb: i already have your FECS/GPCCS, but it's useless without PMU..
00:33 gnurou: something might come for that thanks to GM20B, but... it's still early sadly :/
00:33 gnurou: I hate this situation, it would have made my work much easier if you already got GM204 up and running ;)
00:33 skeggsb: i did manage to upload custom fw to them though recently, and the restrictions on what it can do without being in light secure mode are (sorry...) fucking ridiculous and make no sense from a "security" standpoint..
00:33 skeggsb: hey, i hear you :P
00:34 gnurou: yeah, it doesn't make much sense as of today
00:34 gnurou: in the future I have been told there will be good reasons for that though
00:34 skeggsb: we shall see :)
00:35 skeggsb: it'd have made more sense to block of any ability for gr to do dodgy stuff bypassing the normal vm mechanisms, rather than make it impossible for us to touch gr (it already couldn't touch outside gr prior to gm204) registers...
00:35 skeggsb: but anyway :P
00:35 skeggsb: you don't have control over that, so i'll stop whining :)
00:36 gnurou: I don't even have the knowledge necessary to decide whether this FW thing is good or bad from a security standpoint :)
00:36 gnurou: but I have to assume it makes sense at some point, or we would not go through all the hassle
00:36 skeggsb: i'm more than happy to admit if i'm wrong down the track, but i can't come up with any good reason so far
00:38 gnurou: btw, I should also have asked whether you agree to have nouveau/nvea_* in linux-firmware
00:39 gnurou: the alternative was to load the netlist files, but in the end I preferred to go the "nouveau way" for this
00:39 gnurou: s/files/file, there is only one file at the moment
00:39 skeggsb: that, i'm not sure on. it depends on how you guys will release the firmware stuff in the end i guess.. it'd be nice to not have to switch and support both in the end
00:40 gnurou: that's what I want to avoid too, hence this format
00:41 gnurou:wishes he could use mmiotrace on Tegra
00:41 skeggsb: i wonder if, perhaps, it'd be better to stick them in .fuc.h files like our own is, temporarily
00:41 skeggsb: until we know how the final solution will look
00:42 gnurou: might be... but the license would be a problem I'm afraid
00:42 skeggsb: yeah, that was going to be my disclaimer :P
00:42 gnurou: http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/LICENCE.nvidia
00:42 skeggsb: i don't know (or even want to have to know) the details there, but, i guess linux-firmware in the current format is the best solution to avoid having to find out
00:43 skeggsb: ... or, we can get the firmware situation in general solved first :P
00:43 gnurou: hopefully someone (imirkin?) will get the Nouveau firmware to work directly and using the NV firmware will be optional
00:43 gnurou: ... for GK20A at least
00:44 skeggsb: yeah, gk20a is the only remaining chipset where it's even feasible for us to support directly
00:44 gnurou: :/
00:44 skeggsb: gm10x i solved recently
00:45 skeggsb: i tried a number of questionable work-arounds for gm20x, but didn't get anywhere :(
00:46 skeggsb: once i know what we're going to have to do to properly (the current code is a hack, and blatantly wrong for recent firmware in some ways) support your firmware on gm20x, i'll likely adapt the interfaces to ours to match, to remove the separate paths
00:47 skeggsb: it's all completely up in the air still, which is incredibly frustrating
00:48 gnurou: it is :/
00:55 mlankhorst: skeggsb: yeah bringing up a desktop was a pain, rest was easy. :P
00:56 skeggsb: mlankhorst: i don't suppose you wrote a howto that i can mindlessly follow? :P
00:57 mlankhorst: there are instructions if you don't need xorg-server
00:58 skeggsb: i just want an environment where i can build the drm, to get the gr ucode working
00:58 skeggsb: it shouldn't be overly challenging.. i'm hoping imirkin gets there first secretly :)
00:59 mlankhorst: on tegra? just follow the nouveau instructions
02:13 mupuf: gnurou, skeggsb: what are those netlists you are talking about?
02:27 gnurou: mupuf: files that contain the GR firmwares (FECS/GPCCS, as well as registers packs and other stuff) and distributed by NVIDIA
02:27 gnurou: mupuf: that's how we distribute firmwares for Android - and apparently we also used them for desktop at some point
02:28 mupuf: oh, ok
02:28 mupuf: never heard of them before
02:28 mupuf: gnurou: thanks
02:28 gnurou: yeah I think they are not common for desktop
02:48 mlankhorst: does valgrind-mmt work on arm?
04:34 mlankhorst: joi: it seems that demmt doesn't handle my gk20a trace well, getting tons of
04:34 mlankhorst: w 2:0x0000, 0x20016000
04:34 mlankhorst: w 2:0x0004, 0x0000902d
04:38 mlankhorst: and only pushbuf stuff it sees is PB: 0x00000000 NOP
04:40 mlankhorst: https://mblankhorst.nl/etc/xorg.mmt.xz
10:35 joi: mlankhorst: 403: Forbidden
10:35 mlankhorst: oh sec
10:35 mlankhorst: joi: fixed
10:35 imirkin: valgrind likes to output with 0600 =/
10:36 mlankhorst: seems so..
10:36 specing: makes sense
10:43 joi: mlankhorst: fyi, you seem to be using old mmt version
10:43 mlankhorst: odd
10:43 mlankhorst: just cloned it?
10:44 joi: it should not matter, but..
10:44 mlankhorst: joi: I'm on commit c81744f02f24a2f9ff6df18523145e9e1ded6686 for valgrind
10:44 joi: what's the top commit id?
10:45 joi: weird
10:45 mlankhorst: it's on arm though
10:45 mlankhorst: I'm surprised it works at all :P
10:47 imirkin: why wouldn't it, as long as valgrind has arm support
10:53 mlankhorst: i had issues on i386 with some avx calls that nvidia was making to shove some bits around
10:54 mlankhorst: looks like they have their own memcpy :p
10:54 imirkin: iirc valgrind knows about those now
10:54 imirkin: there was def an issue with sse4.2 a while back
10:54 mlankhorst: yeah it does but mmt didn't
10:54 imirkin: ah :)
10:55 mlankhorst: I fixed it in the 3.8 branch at the time
10:55 mlankhorst: joi: what made you think it was old?
11:01 joi: is it arm64?
11:02 mlankhorst: armhf
11:02 mlankhorst: just arm7l
11:02 joi: which means 32bit?
11:02 mlankhorst: yes
11:06 mlankhorst: it's a system without VRAM though :)
11:11 hrw: hi
11:12 imirkin: mlankhorst: but the cpu doesn't see all memory transactions from the gpu :)
11:12 mlankhorst: probably not
11:12 mlankhorst: but I can see the writes to the push buffer
11:12 hrw: newer kernel, new attempt to get something other than matrox running on aarch64: http://paste.fedoraproject.org/202842/27307085/raw/
11:13 imirkin: right
11:14 mlankhorst: hrw: getting there. :P
11:14 joi: heh, it won't be easy to fix
11:14 mlankhorst: why is channel_del called inside channel_new?
11:15 mlankhorst: joi: ah what's wrong then?
11:16 imirkin: hrw: is there an issue with the pcie device accessing sysram perhaps?
11:17 hrw: imirkin: matrox g550 and sata controller worked
11:17 imirkin: hrw: although that wouldn't cause the exact issue you're having
11:17 mlankhorst: tbh why is channel_del called from channel_new? more useful to figure out what's failing first :P
11:18 imirkin: yeah
11:18 imirkin: sounds like creating a channel is failing and it's doing something bad in teardown
11:18 imirkin: which isn't great _either_ but fixing it won't make your thing work :)
11:18 mlankhorst: channel_init is failing
11:19 joi: mlankhorst: it seems mmt is confused about sizeof(long)!=sizeof(uint64)
11:19 mlankhorst: ah..
11:19 mlankhorst: valgrind-mmt or demmt?
11:22 joi: mostly mmt
11:23 mlankhorst: ah :/
11:23 joi: but demmt also has some issues, because some drm core ioctls are not 64-bit clean..
11:23 mlankhorst: right..
11:23 mlankhorst: but I can fix demmt by compiling it for 32-bits right?
11:23 joi: yeah
11:24 joi: but on mmt side mmap_offsets are stripped off their upper parts, while nouveau uses 64-bit offsets
11:25 joi: I need to install 32-bit os somewhere and figure out what is actually wrong
11:25 mlankhorst: ah..
11:26 joi: hmm, maybe it's arm specific...
11:27 joi: would it be possible to have remote access to your box?
11:28 joi: nvm, it's going to be painful to debug it remotely
11:28 hrw: joi: would like to give but I am probably not allowed. company machine
11:29 joi: hrw: you also have tegra k1?
11:29 joi: ;)
11:30 hrw: ;)
11:30 hrw: too much arm work today. good it was armv8 but too many kernel rebuilds
11:32 mlankhorst: joi: you could probably ask the nice nvidia people for one :)
11:33 mlankhorst: joi: but you can access mine if you want, I can get you a ssh into it and valgrind building should be ok
11:43 mlankhorst: $ time (./autogen.sh; ./configure; make -j4)
11:43 mlankhorst: finished in 9 minutes
12:06 martm: its time for a bit of medical lessons, the concept of chronic pain, its not entirely redicoulous what i am spammed with, cause even with injury on tense moments brain feels more pain, but now with tissue damage which is surrounding a nerve, its a nociceptor neurotransmitter signal, two of the main ones are histamine and serotonine that are harmful for emotions, scar tissue is never about chronic pain only if its close to nerve, it is bit mor
12:06 martm: those are vibration, overstreching or temperature change
12:06 martm: if there is something that makes the cells vibrate nociceptors send neurotransmitter to the brain
12:07 martm: so since i got the injury if my father would not had screwd me, when i would had been relaxed in bed learning stuff until i could heal the scar tissue around the nerve
12:08 martm: i would not had an issue
12:19 imirkin: hrw: might want to boot with nouveau.debug=debug which should help indicate where things are failing
12:19 martm: if you have a cell damage that is in a spot where two bones meet then automatically prequisits are there, and it works bad you need a rest and handle the pain, neuropathy takes quite long to hit, but i faced a terrorist who took this chanche
12:24 martm: not only that they precisely designed the injury they took a possiblity to progress away from hit, and subscribed wrong meds in mental institution
12:25 martm: prescribed sorry
12:25 martm: so anyways, it is usual terror, when someone wants to be killed off
12:25 martm: is wanted to be
12:32 martm: basically you take a med that downregulates histamine, and its done with cleavege via agonist of h3r, it manipulates the stuff good, you feel lot less pain, and abilify is good cause it mainpulates with sedation via h5t receptors the right way too, so the sleep phases are ok
12:32 martm: that is why it is a big hit in world
12:32 mlankhorst: oh right it's josh
12:33 martm: if there is a med that sedates from serotinin 2a and raises histamine, sleep awake cycle is fucked up
12:35 martm: mickeys don't give me that crap dont even try, i know the stuff my own if its terror like past 20years, its that i have to go edventually
12:36 martm: eventually
12:36 martm: bye
12:43 vdpauf: https://devtalk.nvidia.com/default/topic/821171
12:43 vdpauf: "Added support for VDPAU Feature Set F to the NVIDIA VDPAU driver. GPUs with VDPAU Feature Set F are capable of hardware-accelerated decoding of H.265/HEVC video streams."
12:44 vdpauf: someone needs to update http://nouveau.freedesktop.org/wiki/VideoAcceleration/ to add Feature Set F/VP7 to the table
12:47 imirkin: meh
12:47 imirkin: it pretty obviously doesn't work
12:47 imirkin: GM20x is like 97% unsupported by nouveau in the first place...
12:50 vdpauf: Next year, Nvidia Pascal GP1xx family, 100% unsupported, http://blogs.nvidia.com/blog/2015/03/17/pascal/
12:51 imirkin: yep
12:51 imirkin: although hopefully progress will have been made on GM20x's by then
14:29 hrw: imirkin: good point
14:32 hrw: imirkin: did not gave anything more
14:33 imirkin: that's surprising
14:33 imirkin: i would have expected a ton more messages
14:33 imirkin: check for typos?
14:33 hrw: [ 28.030435] nouveau D[ I2C][0000:01:00.0][0x00000000] PAD:X:37: -> PORT:00
14:33 hrw: [ 28.038746] nouveau D[ I2C][0000:01:00.0][0x00000000] PAD:X:37: -> NULL
14:33 hrw: those are extra (3 times)
14:33 imirkin: ah ok, yeah
14:33 imirkin: you should see a ton more
14:34 hrw: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.0.0-0.rc5.git1.3.fc23.hrw1.aarch64 root=UUID=28144985-6cd5-4269-a1a0-bd100589bd74 ro matroxfb_base.xres=1920 matro
14:34 hrw: xfb_base.yres=1080 matroxfb_base.depth=32 matroxfb_base.fv=60 console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000 drm.debug=0x06 nouveau.debug=debug
14:34 imirkin: that seems right
14:34 imirkin: can you pastebin the log?
14:34 hrw: http://paste.fedoraproject.org/202951/73192941
14:35 imirkin: oh, you do get a ton more output
14:36 hrw: ah. scrolled too far in serial output then...
14:36 hrw: 22:36 here
14:36 imirkin: :)
14:36 hrw: it is GF7300SE card
14:37 imirkin: yeah
14:38 imirkin: if you have a more recent nvidia card available, i'd definitely recommend giving that a shot. but this one should work fine too.
14:38 imirkin: (more recent == G80 or newer)
14:38 hrw: I know
14:38 hrw: just do not want to spend money on not needed stuff
14:38 imirkin: sure. i just figured you might have one lying around
14:38 hrw: ;)
14:39 hrw: radeon hd5450, matrox g550, nvidia 7300gs, radeon r7 240 are all pcie gfx cards I have now
14:39 hrw: and r7 one sits in my desktop
14:40 hrw: had nvidia gts 250 but got rid of it - it was louder than my vacuum cleaner
14:43 hrw: ideas what to look at?
14:45 imirkin: hrw: figure out why nouveau_channel_new is failing and why it's hitting nouveau_channel_del
14:45 imirkin: as a side-thing, you could see why it blows up the universe when it does that
14:45 imirkin: but... if you fix it, that just means it'll fail driver init gracefully, not leave you with a working card :)
14:45 hrw: I know
14:46 hrw: once I had some ugly hack which did sth like that
14:48 hrw: the worst part is that each tweak to module will probably require reboot
14:48 hrw: which can take up to 3-4 minutes
14:48 imirkin: hrw: so perhaps fix the load fail first then
14:49 imirkin: then you can load/unload at will
15:18 calim: imirkin: have you tried turnin off the watchdog ?
15:18 calim: ref. loops with high iteration count
15:19 imirkin: calim: no, i only found out about that recently
15:19 imirkin: calim: and i don't have a nv50 plugged in, and no one has volunteered to test
15:19 calim: run with NOUVEAU_SHADER_WATCHDOG=FALSE
15:19 calim: hm
15:20 imirkin: calim: btw, i sent a patch to fix postfactor stuff... let me know if it makes sense to you
15:20 hrw: [ 8.957475] Console: switching to colour frame buffer device 240x67
15:20 hrw: [ 8.970845] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
15:20 hrw: imirkin: added nouveau.noaccel=1
15:20 imirkin: we were peepholing mul's into neg/etc without taking the postfactor into account
15:20 imirkin: hrw: that will have obvious downsides :)
15:20 imirkin: like... no accel :)
15:21 hrw: but works and I have text console
15:22 hrw: X11 driver does not want to work but that's other issue
15:22 hrw: fbdev one works
15:23 imirkin: hmmm... what does the ddx complain about?
15:23 hrw: http://paste.fedoraproject.org/202967/32218014/
15:23 imirkin: 404
15:23 hrw: retry?
15:23 imirkin: nope
15:24 hrw: hm
15:24 calim: imirkin: yes, looks good
15:26 hrw: heh. fedora fscked up pastebinit tool
15:26 imirkin: ah there it goes
15:27 imirkin: weird. "no devices detected".
15:27 imirkin: [ 118.106] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
15:27 imirkin: ah yes. systemd. enjoy.
15:28 hrw: imirkin: http://pastebin.ca/2964361
15:29 hrw: will run login manager
15:29 imirkin: hrw: right, that has the same error
15:30 hrw: heh. lightdm segfaults
15:32 hrw: http://pastebin.ca/2964363 kdm
15:57 skeggsb: gnurou: you guys definitely *used* to use them for gf100 and up :)
15:57 skeggsb: (netlists)
16:00 hrw: bye
21:21 gnurou: skeggsb: you know better than me, I have never worked on desktop GPUs :P
22:59 NolanSyKinsley: I am having issues, 2D seems fine but for 3d I just get http://i.imgur.com/Ld6m4Jh.png and http://i.imgur.com/ynFiQN8.png I am running Manjaro with a 9800gt (NV50) I used it's hardware detect to install nouveau.