Mark Fortescue wrote: > Hi, > > Why don't you just move the VMALLOC area to say FC000000. I did this on my > sparc32 system to alow me to debug some PROM Console/CG3 issues. I did not > observe any failures/anomalies with this and is gets around any problems > with the PROM memory mapping of frame buffers. Sounds like a good idea, but SRMMU_NOCACHE occupies FC000000, and then highmem mappings (PKMAP_BASE) are after that. However, if the nocache and highmem mappings are not used on sun4c, we may be able to move them below F0000000. > It also has the advantage of alowing you to increase the size of the > VMALLOC area should this be required. > > Ideally, the area should be dynamically allocated based on the required > size and the PROM allocations on boot but this may be somewhat > impractical in real life. > > Regards > Mark Fortescue. > - To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
