Re: [PATCH 13/30] viafb: Separate global and fb-specific data

Jonathan Corbet
2010-04-30T18:23:00Z

On Fri, 30 Apr 2010 20:07:02 +0200
Florian Tobias Schandinat <FlorianSchandinat@gmx.de> wrote:

> Please don't do this. The reason for not failing in viafb is that
> ioremap failure of the engine is not critical it just disables the
> hardware acceleration but otherwiese it works quite nice. The problem is
> that ioremap failures are quite common as we really try to remap huge
> amount (sometimes above 128 or even 256 MB).

But...this region is small should never be hard to remap. Are you sure
you've seen trouble with the engine region?

> In fact the bug (or missing
> feature) is that the first ioremap is fatal and that needs to be fixed
> on the long run. Sorry but I don't want to make viafb unusable for many
> people if they don't add the "vmalloc=" kernel option so failing here
> would be a step in the wrong direction.

Is the real problem, perhaps, that we're remapping the entire
framebuffer? One wonders if we could get away without doing that.
Some quick greppery suggests that the cursor code goes straight to a
small region of framebuffer memory. With working acceleration, we
shouldn't need cfb_*(). But, probably, I'm missing something?

Meanwhile, I can let initialization continue without the engine space.
It kills interrupts/dma/camera, of course, but so be it.

jon