The patch titled
tridentfb: y-panning fixes
has been removed from the -mm tree. Its filename was
tridentfb-y-panning-fixes.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: tridentfb: y-panning fixes
From: Krzysztof Helt <krzysztof.h1@xxxxx>
The Trident cards uses only 20-bit address of screen start in double
words. This allows addressing for only 4MB of video memory so check this.
Also remove some redundant checks and assignments.
Signed-off-by: Krzysztof Helt <krzysztof.h1@xxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/video/tridentfb.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff -puN drivers/video/tridentfb.c~tridentfb-y-panning-fixes drivers/video/tridentfb.c
--- a/drivers/video/tridentfb.c~tridentfb-y-panning-fixes
+++ a/drivers/video/tridentfb.c
@@ -870,8 +870,10 @@ static int tridentfb_check_var(struct fb
line_length = var->xres_virtual * bpp / 8;
}
- if (var->yres > var->yres_virtual)
- var->yres_virtual = var->yres;
+ /* datasheet specifies how to set panning only up to 4 MB */
+ if (line_length * (var->yres_virtual - var->yres) > (4 << 20))
+ var->yres_virtual = ((4 << 20) / line_length) + var->yres;
+
if (line_length * var->yres_virtual > info->fix.smem_len)
return -EINVAL;
@@ -944,8 +946,6 @@ static int tridentfb_pan_display(struct
debug("enter\n");
offset = (var->xoffset + (var->yoffset * var->xres_virtual))
* var->bits_per_pixel / 32;
- info->var.xoffset = var->xoffset;
- info->var.yoffset = var->yoffset;
set_screen_start(par, offset);
debug("exit\n");
return 0;
@@ -1225,7 +1225,6 @@ static int tridentfb_setcolreg(unsigned
((blue & 0xFF00) >> 8);
}
-/* debug("exit\n"); */
return 0;
}
_
Patches currently in -mm which might be from krzysztof.h1@xxxxx are
origin.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
