search for: timing_entry_length

Displaying 3 results from an estimated 3 matches for "timing_entry_length".

[PATCH envytools] Fix range end to the last value of timing table.
2014 Aug 25
2
[PATCH envytools] Fix range end to the last value of timing table.
...6486..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) - conf->range.end = conf->vbios.timing_entry_length; + conf->range.end = conf->vbios.timing_entry_length-1; fprintf(stderr, "Shallow mode: Will iterate between %i and %i\n", conf->range.start, conf->range.end); -- 1.9.1
[PATCH envytools] nvbios: Fix reading of ram_restrict_group_count.
2014 Aug 30
3
[PATCH envytools] nvbios: Fix reading of ram_restrict_group_count.
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 @@
[PATCH envytools] Fix range end to the last value of timing table.
2014 Aug 28
0
[PATCH envytools] Fix range end to the last value of timing table.
...t_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) > - conf->range.end = conf->vbios.timing_entry_length; > + conf->range.end = conf->vbios.timing_entry_length-1; > > fprintf(stderr, "Shallow mode: Will iterate between %i and %i\n", conf->range.start, conf->range.end); > Hey I don't like this patch because it would create an output difference between t...