P

Powerpc-utils

Settings | Report Duplicate

0

I Use This!

Activity Not Available

Commits : Listings

Analyzed 8 months ago. based on code collected about 1 year ago.

Commit Message	Contributor	Files Modified	Lines Added	Lines Removed	Code Location	Date
Jan 04, 2023 — Jan 04, 2024 Showing page 45 of 64 Search / Filter on:
The 'Desired Variable Capacity Weight' field in the output from lparstat -i is reported twice. This patch removes one of them so that it is only reported once.	Nathan Fontenot	More...				over 11 years ago
The 'Desired Variable Capacity Weight' field in the output from lparstat -i	nathan.fontenot	More...				over 11 years ago
The 'Desired Variable Capacity Weight' field in the output from lparstat -i is reported twice. This patch removes one of them so that it is only reported once.	Nathan Fontenot	More...				over 11 years ago
This patch does a lot of cleanup of the indentation in places to use 4 spaces instead of tabs. Note, this is not really what is preferred but what is used by this script, this change tries to make indentation consistent in the script.	Nathan Fontenot	More...				over 11 years ago
This patch does a lot of cleanup of the indentation in places to use 4	nathan.fontenot	More...				over 11 years ago
This patch does a lot of cleanup of the indentation in places to use 4 spaces instead of tabs. Note, this is not really what is preferred but what is used by this script, this change tries to make indentation consistent in the script.	Nathan Fontenot	More...				over 11 years ago
The bootlist command uses the ofpathname command to convert between logical device names and Open Firmware device path names. The current use of ofpathname does not correctly interpret the output and whether the ofpathname call succeeds or not.	Nathan Fontenot	More...				over 11 years ago
The bootlist command uses the ofpathname command to convert between	nathan.fontenot	More...				over 11 years ago
The bootlist command uses the ofpathname command to convert between logical device names and Open Firmware device path names. The current use of ofpathname does not correctly interpret the output and whether the ofpathname call succeeds or not.	Nathan Fontenot	More...				over 11 years ago
The man page and usages statement incorrectly specify the -m option as the only required option. One can run the command and only specify the -m option, but this results in the script doing nothing.	Nathan Fontenot	More...				over 11 years ago
The man page and usages statement incorrectly specify the -m option	nathan.fontenot	More...				over 11 years ago
The man page and usages statement incorrectly specify the -m option as the only required option. One can run the command and only specify the -m option, but this results in the script doing nothing.	Nathan Fontenot	More...				over 11 years ago
The call to do_update on a remove property doesn't account for the null terminator in the length and results in the last character of the property name being truncated in the log.	Tyrel Datwyler	More...				over 11 years ago
The call to do_update on a remove property doesn't account for the null	tyrel.datwyler	More...				over 11 years ago
The call to do_update on a remove property doesn't account for the null terminator in the length and results in the last character of the property name being truncated in the log.	Tyrel Datwyler	More...				over 11 years ago
The say() logging function allocates a static 256 byte buffer for messages. Messages passed to say() larger than 256 bytes result in a truncated message followed by garbage from past the end of the buffer being written to the log file. This is a result of using the return value of vsnprintf as the length input to the write function. Despite only writing no more than 256 bytes (including the trailing \0) to the buffer the return value of vsnprintf is actually the total number of bytes (not including the trailing \0) that would have been written had the buffer been long enough.	Tyrel Datwyler	More...				over 11 years ago
The say() logging function allocates a static 256 byte buffer for	tyrel.datwyler	More...				over 11 years ago
The say() logging function allocates a static 256 byte buffer for messages. Messages passed to say() larger than 256 bytes result in a truncated message followed by garbage from past the end of the buffer being written to the log file. This is a result of using the return value of vsnprintf as the length input to the write function. Despite only writing no more than 256 bytes (including the trailing \0) to the buffer the return value of vsnprintf is actually the total number of bytes (not including the trailing \0) that would have been written had the buffer been long enough.	Tyrel Datwyler	More...				over 11 years ago
This patch corrects the parsing of the work area buffer returned by	tyrel.datwyler	More...				over 11 years ago
This patch corrects the parsing of the work area buffer returned by ibm,update-properties. The first property descriptor is slightly different from the rest of the properties returned and needs to be handled accordingly.	Tyrel Datwyler	More...				over 11 years ago
This patch corrects the parsing of the work area buffer returned by ibm,update-properties. The first property descriptor is slightly different from the rest of the properties returned and needs to be handled accordingly.	Tyrel Datwyler	More...				over 11 years ago
Rewrote update_flash man page. Also included below details: - Explaination of when temporary image is committed to permanent side during firmware update. - Information on -s and -n option. - Added exit status. - Added few examples.	Vasant Hegde	More...				almost 12 years ago
Rewrote update_flash man page. Also included below details: - Explaination of when temporary image is committed to permanent side during firmware update. - Information on -s and -n option. - Added exit status. - Added few examples.	Vasant Hegde	More...				almost 12 years ago
Rewrote update_flash man page. Also included below details:	vasant.hegde	More...				almost 12 years ago
Add new return code to check firmware entitlement expiry. Also display firmware GA date and system firmware entitlement expiry date, when we try to flash expired image (image GA date is beyond system entitlement date).	Vasant Hegde	More...				almost 12 years ago
Add new return code to check firmware entitlement expiry.	vasant.hegde	More...				almost 12 years ago
Add new return code to check firmware entitlement expiry. Also display firmware GA date and system firmware entitlement expiry date, when we try to flash expired image (image GA date is beyond system entitlement date).	Vasant Hegde	More...				almost 12 years ago
If machine supports two image areas and machine is running from temporary side of image, then attempt to update flash image may automatically commit temporary side of image to Permanent side.	Vasant Hegde	More...				almost 12 years ago
If machine supports two image areas and machine is running from temporary side of image, then attempt to update flash image may automatically commit temporary side of image to Permanent side.	Vasant Hegde	More...				almost 12 years ago
If machine supports two image areas and machine is running from	vasant.hegde	More...				almost 12 years ago

←
1
2
…
41
42
43
44
45
46
47
48
49
…
63
64
→