| Paul Mackerras | 14cf11a | 2005-09-26 16:04:21 +1000 | [diff] [blame] | 1 | |
| 2 | config PREP_RESIDUAL |
| 3 | bool "Support for PReP Residual Data" |
| 4 | depends on PPC_PREP |
| 5 | help |
| 6 | Some PReP systems have residual data passed to the kernel by the |
| 7 | firmware. This allows detection of memory size, devices present and |
| 8 | other useful pieces of information. Sometimes this information is |
| 9 | not present or incorrect, in which case it could lead to the machine |
| 10 | behaving incorrectly. If this happens, either disable PREP_RESIDUAL |
| 11 | or pass the 'noresidual' option to the kernel. |
| 12 | |
| 13 | If you are running a PReP system, say Y here, otherwise say N. |
| 14 | |
| 15 | config PROC_PREPRESIDUAL |
| 16 | bool "Support for reading of PReP Residual Data in /proc" |
| 17 | depends on PREP_RESIDUAL && PROC_FS |
| 18 | help |
| 19 | Enabling this option will create a /proc/residual file which allows |
| 20 | you to get at the residual data on PReP systems. You will need a tool |
| 21 | (lsresidual) to parse it. If you aren't on a PReP system, you don't |
| 22 | want this. |