25edd6946a
This is based upon a report by Meelis Roos showing that it's possible that we'll try to fetch a property that is 32K in size with some devices. With the current fixed 3K buffer we use for moving data in and out of the firmware during PROM calls, that simply won't work. In fact, it will scramble random kernel data during bootup. The reasoning behind the temporary buffer is entirely historical. It used to be the case that we had problems referencing dynamic kernel memory (including the stack) early in the boot process before we explicitly told the firwmare to switch us over to the kernel trap table. So what we did was always give the firmware buffers that were locked into the main kernel image. But we no longer have problems like that, so get rid of all of this indirect bounce buffering. Besides fixing Meelis's bug, this also makes the kernel data about 3K smaller. It was also discovered during these conversions that the implementation of prom_retain() was completely wrong, so that was fixed here as well. Currently that interface is not in use. Reported-by: Meelis Roos <mroos@linux.ee> Tested-by: Meelis Roos <mroos@linux.ee> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
|---|---|---|
| .. | ||
| bootstr_32.c | ||
| bootstr_64.c | ||
| cif.S | ||
| console_32.c | ||
| console_64.c | ||
| devmap.c | ||
| devops_32.c | ||
| devops_64.c | ||
| init_32.c | ||
| init_64.c | ||
| Makefile | ||
| memory.c | ||
| misc_32.c | ||
| misc_64.c | ||
| mp.c | ||
| p1275.c | ||
| palloc.c | ||
| printf.c | ||
| ranges.c | ||
| segment.c | ||
| tree_32.c | ||
| tree_64.c | ||