Re: vmalloc can clobber framebuffer on sparc32

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.


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.

On Mon, 12 Jun 2006, David Miller wrote:

> 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
> 

-
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

[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux