From: Bob Breuer <breuerr@xxxxxx> Date: Mon, 12 Jun 2006 01:43:25 -0500 > after rearrange and fill gaps: > start - end ( size ) type > 00000000-fe3fffff (fe400000) free > fe400000-fe6fffff (00300000) free > fe600000 = VMALLOC_START > fe700000-feefffff (00800000) unavail (cg14 framebuffer) > fef00000-ffcfffff (00e00000) free > ffc00000 = VMALLOC_END > ffd00000-ffd25fff (00026000) free > ffd26000-ffe3efff (00119000) unavail > ffe3f000-ffebffff (00081000) free > ffec0000-ffefffff (00040000) unavail > fff00000-ffffffff (00100000) free > > The framebuffer sitting in the middle of the vmalloc range is what > causes the problem. Ok. Let's take a peek at what NetBSD thinks about the layout here... They assume the same start and end address for openprom. What we should probably do is explicitly sbus_ioremap() the framebuffer on sparc32 even if OBP has a mapping setup already. And then just clear out the areas outside of the kernel image and the reserved OBP area. I wonder if this will break things like promcons :( - 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