search for: timing_entry_high

Displaying 5 results from an estimated 5 matches for "timing_entry_high".

2014 Aug 31
2
[PATCH envytools] nvamemtiming: Handle target < initial case when iterating values
...e order, try: >> sudo nvamemtiming pramin 0x6a22 5 0 -d 3 >> > Ok. It's intended then. Thanks! I totally agree that this tool is a little confusing. If you have suggestions on how to improve the usage doc, feel free to propose me something better :) fprintf(stderr, "\t-d timing_entry_high: For each indexes, iterate between the timing_entry and the timing_entry_high value (Deep mode)\n"); Speaking about this, this should be corrected to "For each index", no plural after each. I'll fix it right now.
2014 Aug 31
1
[PATCH envytools] nvamemtiming: Handle target < initial case when iterating values
...>>> >>> Ok. It's intended then. Thanks! >> >> I totally agree that this tool is a little confusing. If you have >> suggestions on how to improve the usage doc, feel free to propose me >> something better :) >> >> fprintf(stderr, "\t-d timing_entry_high: For each indexes, iterate >> between the timing_entry and the timing_entry_high value (Deep >> mode)\n"); >> >> Speaking about this, this should be corrected to "For each index", no >> plural after each. I'll fix it right now. >> > Ok. I...
2014 Aug 31
0
[PATCH envytools] nvamemtiming: Handle target < initial case when iterating values
...ming pramin 0x6a22 5 0 -d 3 >>> >> Ok. It's intended then. Thanks! > > I totally agree that this tool is a little confusing. If you have > suggestions on how to improve the usage doc, feel free to propose me > something better :) > > fprintf(stderr, "\t-d timing_entry_high: For each indexes, iterate > between the timing_entry and the timing_entry_high value (Deep mode)\n"); > > Speaking about this, this should be corrected to "For each index", no > plural after each. I'll fix it right now. > Ok. I will think about it. Some comments...
2014 Aug 31
2
[PATCH envytools] nvamemtiming: Handle target < initial case when iterating values
On 31/08/2014 16:01, Christian Costa wrote: > Le 31/08/2014 15:12, Martin Peres a ?crit : >> On 31/08/2014 15:00, Christian Costa wrote: >>> Otherwise some values are not tested at all. >> I would rather have a warning than the program doing stuff behind my >> back. This is a dev tool, dumb == good ;) >> > But why didn't you call it Dumb mode rather that
2014 Aug 31
6
[PATCH envytools] nvbios: Add missing null byte to string read from file.
--- 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 =