similar to: [PATCH envytools] nva: Clean up nva tools doc

- Sort commands by name for easier update - Make more readable - Remove no more existing commands --- nva/README | 83 +++++++++++++++++++++++++++++++++----------------------------- 1 file changed, 44 insertions(+), 39 deletions(-) diff --git a/nva/README b/nva/README index 625ea7c..d4347c5 100644 --- a/nva/README +++ b/nva/README @@ -3,7 +3,7 @@ registers. WARNING: these tools *can* and

On Mon, Aug 25, 2014 at 6:35 PM, Martin Peres <martin.peres at free.fr> wrote: > On 25/08/2014 20:58, Christian Costa wrote: >> >> - Sort commands by name for easier update >> - Make more readable >> - Remove no more existing commands >> --- >> nva/README | 83 >> +++++++++++++++++++++++++++++++++----------------------------- >> 1 file

On 25/08/2014 20:58, Christian Costa wrote: > - Sort commands by name for easier update > - Make more readable > - Remove no more existing commands > --- > nva/README | 83 +++++++++++++++++++++++++++++++++----------------------------- > 1 file changed, 44 insertions(+), 39 deletions(-) > > diff --git a/nva/README b/nva/README > index 625ea7c..d4347c5 100644 > ---

--- nva/.gitignore | 53 +++++++++++++++++++++++++++-------------------------- 1 file changed, 27 insertions(+), 26 deletions(-) diff --git a/nva/.gitignore b/nva/.gitignore index 5c9184b..72de056 100644 --- a/nva/.gitignore +++ b/nva/.gitignore @@ -1,39 +1,40 @@ +evotiming +libnva.a +libnva.so +nv01dump +nv01post +nvacounter +nvadownload +nvaevo +nvafakebios nvafill +nvaforcetemp +nvafucstart

--- rnndb/memory/nvc0_pbfb.xml | 37 ++++++++++++++++++++++++++++++++++--- 1 file changed, 34 insertions(+), 3 deletions(-) diff --git a/rnndb/memory/nvc0_pbfb.xml b/rnndb/memory/nvc0_pbfb.xml index 500cea9..e006dbe 100644 --- a/rnndb/memory/nvc0_pbfb.xml +++ b/rnndb/memory/nvc0_pbfb.xml @@ -49,23 +49,54 @@ Most bitfields are unknown. </doc> <bitfield high="7"

--- nvbios/nvbios.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/nvbios/nvbios.c b/nvbios/nvbios.c index f7aafe3..28e62ad 100644 --- a/nvbios/nvbios.c +++ b/nvbios/nvbios.c @@ -774,11 +774,12 @@ int set_strap_from_string(const char* strap_s) int set_strap_from_file(const char *path) { FILE *strapfile = NULL; - char tmp[21]; + char tmp[22]; strapfile =

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #57 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #55) > > > [aloew at aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10 > > > WARN: Can't probe 0000:01:00.0 > > > PCI init failure! > > > You need to run these as root. > > Ouch - sorry - could have indeed

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #55 from Andreas Loew <awl1 at gmx.net> --- > > [aloew at aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10 > > WARN: Can't probe 0000:01:00.0 > > PCI init failure! > You need to run these as root. Ouch - sorry - could have indeed had this idea myself... :-( Here are the results as root: [aloew at

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #60 from Andreas Loew <awl1 at gmx.net> --- > There was a bug in nvapeek/poke (it was using the wrong address space by > default), can you update your pull and try again? [That explains why you saw > 'S' in the output.] Of course - here you are: The version I used is from the "Download ZIP" button in

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #54 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #52) > Hello again, Ilia, > > > Can you grab envytools (https://github.com/envytools/envytools) and run > > bad news (or maybe expected from what we have been seeing earlier): > > [aloew at aloew-lap envytools-master]$

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #52 from Andreas Loew <awl1 at gmx.net> --- Hello again, Ilia, > Can you grab envytools (https://github.com/envytools/envytools) and run bad news (or maybe expected from what we have been seeing earlier): [aloew at aloew-lap envytools-master]$ ./nva/nvapeek 10200c WARN: Can't probe 0000:01:00.0 PCI init failure!

--- nva/set_timings.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nva/set_timings.c b/nva/set_timings.c index 7376486..985a707 100644 --- a/nva/set_timings.c +++ b/nva/set_timings.c @@ -506,7 +506,7 @@ shallow_dump(struct nvamemtiming_conf *conf) if (conf->range.start == (unsigned char) -1) conf->range.start = 0; if (conf->range.end == (unsigned char) -1) -

On 25/08/2014 21:00, Christian Costa wrote: > --- > nva/set_timings.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/nva/set_timings.c b/nva/set_timings.c > index 7376486..985a707 100644 > --- a/nva/set_timings.c > +++ b/nva/set_timings.c > @@ -506,7 +506,7 @@ shallow_dump(struct nvamemtiming_conf *conf) > if (conf->range.start ==

Otherwise some values are not tested at all. --- nva/set_timings.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/nva/set_timings.c b/nva/set_timings.c index 6cd831c..7a8f845 100644 --- a/nva/set_timings.c +++ b/nva/set_timings.c @@ -408,7 +408,7 @@ static void iterate_values(struct nvamemtiming_conf *conf, FILE *outf, uint8_t index, enum color color) { uint8_t

The entry offset was use instead of the data it points to. Probably a regression. The files showing script parsing errors has been reduced from 410 to 6 with the database of 505 vbios. --- nvbios/mem.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nvbios/mem.c b/nvbios/mem.c index 81f2d1b..e4797e3 100644 --- a/nvbios/mem.c +++ b/nvbios/mem.c @@ -232,11 +232,11 @@

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #69 from Andreas Loew <awl1 at gmx.net> --- > Could you provide the output of > > nvapeek 154c > nvapeek 1540 > > Those registers specify which engines are there. I think we're ignoring them > in nouveau... OK - that might indeed explain the issues seen... Here you are: [aloew at aloew-lap nva]$ sudo

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #58 from Andreas Loew <awl1 at gmx.net> --- > > [aloew at aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c 10 > > 0010200c: SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS > > nvapeek 10200c without the 10. (Not sure what that does.... maybe reads out > 0x10 regs) yes - seems to read 10 registers:

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #51 from Ilia Mirkin <imirkin at alum.mit.edu> --- So actually I'm told that pcrypt is on the main clock, so that theory is out. Can you grab envytools (https://github.com/envytools/envytools) and run nvapeek 10200c nvapoke 10200c 10 nvapeek 10200c and see what's in dmesg?Do you see additional MMIO read/write failures,

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #62 from Andreas Loew <awl1 at gmx.net> --- But generally, nvapeek seems to work fine now: [aloew at aloew-lap nva]$ sudo ./nvapeek 0 00000000: 086a00a2 Looking forward to your comments... BR, Andreas -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #65 from Andreas Loew <awl1 at gmx.net> --- Oops - I just remembered that I am booting my kernel with "nouveau.config=PCRYPT=0" in the meantime... Does this make any difference, i.e. do I need to retry the nvapeek/nvapoke sequence without this kernel option? Sorry & thanks, Andreas -- You are receiving this