gmane.linux.fbdev.devel

[PATCH 4/4] fbcon: Replace vc_cursor_type mask0x10 with CUR_USE_SW

Henry Nestler — 2009-12-02T02:59:43

from: Henry Nestler <henry.nestler< at >gmail.com>

Replace hard coded vc_cursor_type mask 0x10 with macro CUR_USE_SW.

Signed-off-by: Henry Nestler <henry.nestler< at >gmail.com>
---

This patch depends on [patch 3/4], because it used new macro CUR_USE_SW 0x10.

Kernel version 2.6.32-rc8

 drivers/video/console/tileblit.c        |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/video/console/tileblit.c b/drivers/video/console/tileblit.c
--- a/drivers/video/console/tileblit.c
+++ b/drivers/video/console/tileblit.c
< at >< at > -83,7 +83,7 < at >< at > static void tile_cursor(struct vc_data *vc, struct
fb_info *info, int mode,
 int softback_lines, int fg, int bg)
 {
 struct fb_tilecursor cursor;
-int use_sw = (vc->vc_cursor_type & 0x10);
+int use_sw = (vc->vc_cursor_type & CUR_USE_SW);

 cursor.sx = vc->vc_x;
 cursor.sy = vc->vc_y;
===

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on v

[PATCH 3/4] fbcon: Bugfix soft cursor detectionin Tile Blitting

Henry Nestler — 2009-12-02T02:52:56

from: Henry Nestler <henry.nestler< at >gmail.com>

Use mask 0x10 for "soft cursor" detection on in function tile_cursor.
(Tile Blitting Operation in framebuffer console).

The old mask 0x01 for vc_cursor_type detects CUR_NONE, CUR_LOWER_THIRD
and every second mode value as "software cursor". This hides the cursor
for these modes (cursor.mode = 0). But, only CUR_NONE or "software cursor"
should hide the cursor.

Signed-off-by: Henry Nestler <henry.nestler< at >gmail.com>
---
Kernel version 2.6.32-rc8

 drivers/video/console/tileblit.c        |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/video/console/tileblit.c b/drivers/video/console/tileblit.c
index 0056a41..15e8e1a 100644
--- a/drivers/video/console/tileblit.c
+++ b/drivers/video/console/tileblit.c
< at >< at > -83,7 +83,7 < at >< at > static void tile_cursor(struct vc_data *vc, struct
fb_info *info, int mode,
 int softback_lines, int fg, int bg)
 {
 struct fb_tilecursor cursor;
-int use_sw = (vc->vc_cursor_type & 0x01);
+int use_sw = (vc->vc_

[PATCH 2/4] fbcon: Macro CUR_USE_SW forvc_cursor_type mask 0x10

Henry Nestler — 2009-12-02T02:50:09

from: Henry Nestler <henry.nestler< at >gmail.com>

Replace hard coded 0x10 mask for vc_cursor_type with new macro CUR_USE_SW.

Signed-off-by: Henry Nestler <henry.nestler< at >gmail.com>
---
Kernel version 2.6.32-rc8

 drivers/char/vt.c                       |    2 +-
 drivers/video/console/bitblit.c         |    2 +-
 drivers/video/console/fbcon.c           |    2 +-
 drivers/video/console/fbcon_ccw.c       |    2 +-
 drivers/video/console/fbcon_cw.c        |    2 +-
 drivers/video/console/fbcon_ud.c        |    2 +-
 include/linux/console_struct.h          |    1 +
 7 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/drivers/char/vt.c b/drivers/char/vt.c
index 0c80c68..f8b0f58 100644
--- a/drivers/char/vt.c
+++ b/drivers/char/vt.c
< at >< at > -566,7 +566,7 < at >< at > static void add_softcursor(struct vc_data *vc)
 int i = scr_readw((u16 *) vc->vc_pos);
 u32 type = vc->vc_cursor_type;

-if (! (type & 0x10)) return;
+if (! (type & CUR_USE_SW)) return;
 if (softcursor_original != -1) return;
 softcursor_original = i;

[patch] fix oops with no /proc

Dan Carpenter — 2009-11-22T14:21:11

Fixed a typo:  missing *.  This would lead to a kernel oops if the kernel
was compiled without support for the /proc file system.

Found with a static checker.  Compile tested.

regards,
dan carpenter

Signed-off-by: Dan Carpenter <error27< at >gmail.com>

--- orig/drivers/video/via/viafbdev.c2009-11-21 14:44:33.000000000 +0200
+++ devel/drivers/video/via/viafbdev.c2009-11-21 14:44:43.000000000 +0200
< at >< at > -1797,7 +1797,7 < at >< at > static const struct file_operations viaf
 static void viafb_init_proc(struct proc_dir_entry **viafb_entry)
 {
 *viafb_entry = proc_mkdir("viafb", NULL);
-if (viafb_entry) {
+if (*viafb_entry) {
 proc_create("dvp0", 0, *viafb_entry, &viafb_dvp0_proc_fops);
 proc_create("dvp1", 0, *viafb_entry, &viafb_dvp1_proc_fops);
 proc_create("dfph", 0, *viafb_entry, &viafb_dfph_proc_fops);

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and de

drm_fb_helper: Impossible to change video mode

Paulius Zaleckas — 2009-11-20T13:16:28

Hi,

On drivers using drm_fb_helper's in fb_ops it is not possible to change
video mode, because of different var->pixclock evaluation:

int drm_fb_helper_check_var(struct fb_var_screeninfo *var,
    struct fb_info *info)
{
[...]
if (var->pixclock == -1 || !var->pixclock)
return -EINVAL;
[...]

int drm_fb_helper_set_par(struct fb_info *info)
{
[...]
if (var->pixclock != -1) {
DRM_ERROR("PIXEL CLCOK SET\n");
return -EINVAL;
}
[...]

One of these evaluations will fail regardless of pixclock value.

P.S. check CLCOK spelling :)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

i810fb: fix wrong pixclock for discrete modeselection

Krzysztof Helt — 2009-11-19T17:58:01

From: Krzysztof Helt <krzysztof.h1< at >wp.pl>

If the i810fb driver is configured for use only predefined discrete video modes
the wrong pixclock value is used. The par->regs.pixclock value is a value from
the previous mode when a video mode is switched. It results in unreadable screen
if the old video mode has higher resolution and the new mode with the old (high)
pixclock is outside attached monitor's specs.

Signed-off-by: Krzysztof Helt <krzysztof.h1< at >wp.pl>
---
I have noticed this testing the patch named "i810fb: Fix stack exploding".

This patch requires my patch send to Alan Cox and Andrew Morton 
named "i810fb: Fix stack exploding".

--- drivers/video/i810/i810_dvt.c~2009-11-17 19:38:11.002864450 +0100
+++ drivers/video/i810/i810_dvt.c2009-11-19 18:48:52.518846238 +0100
< at >< at > -233,7 +233,7 < at >< at > static int i810fb_find_best_mode(u32 xre
 void i810fb_encode_registers(const struct fb_var_screeninfo *var,
      struct i810fb_par *par, u32 xres, u32 yres)
 {
-u32 i_best = i810fb_find_best_mode(xres, yres, par-

[PATCH 4/8] pxa: delete redundant vsync/hsyncrevert flag

Jun Nie — 2009-11-16T09:34:39

From: Jun Nie <njun< at >marvell.com>
Date: Tue, 10 Nov 2009 15:11:36 +0800
Subject: [PATCH] pxa: delete redundant vsync/hsync revert flag
var.sync can cover its function

Signed-off-by: Jun Nie <njun< at >marvell.com>
---
 include/video/pxa168fb.h |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/include/video/pxa168fb.h b/include/video/pxa168fb.h
index 01c18bc..53919fe 100644
--- a/include/video/pxa168fb.h
+++ b/include/video/pxa168fb.h
< at >< at > -143,8 +143,6 < at >< at > struct pxa168fb_mach_info {
 unsignedinvert_composite_blank:1;
 unsignedinvert_pix_val_ena:1;
 unsignedinvert_pixclock:1;
-unsignedinvert_vsync:1;
-unsignedinvert_hsync:1;
 unsignedpanel_rbswap:1;
 unsignedactive:1;
 unsignedenable_lcd:1;

[PATCH 3/8] pxa: fix offset setting atinitialization

Jun Nie — 2009-11-16T09:34:32

From: Jun Nie <njun< at >marvell.com>
Date: Tue, 10 Nov 2009 09:33:49 +0800
Subject: [PATCH] pxa: fix offset setting at initialization

Signed-off-by: Jun Nie <njun< at >marvell.com>
---
 drivers/video/pxa168fb.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/video/pxa168fb.c b/drivers/video/pxa168fb.c
index e728be3..6283c16 100644
--- a/drivers/video/pxa168fb.c
+++ b/drivers/video/pxa168fb.c
< at >< at > -765,6 +765,7 < at >< at > static int __init pxa168fb_probe(struct
platform_device *pdev)
 }

 info->fix.smem_start = (unsigned long)fbi->fb_start_dma;
+set_graphics_start(info, 0, 0);

 /*
  * Set video mode according to platform data.

[PATCH 2/8] pxa: support PXA168 LCD platformdependent power on

Jun Nie — 2009-11-16T09:34:27

From: Jun Nie <njun< at >marvell.com>
Date: Mon, 16 Nov 2009 17:16:35 +0800
Subject: [PATCH] pxa: support PXA168 LCD platform dependent power on

Signed-off-by: Jun Nie <njun< at >marvell.com>
---
 drivers/video/pxa168fb.c |   17 +++++++++++++++++
 1 files changed, 17 insertions(+), 0 deletions(-)

diff --git a/drivers/video/pxa168fb.c b/drivers/video/pxa168fb.c
index aec95c4..e728be3 100644
--- a/drivers/video/pxa168fb.c
+++ b/drivers/video/pxa168fb.c
< at >< at > -845,6 +845,23 < at >< at > static int __init pxa168fb_probe(struct
platform_device *pdev)
 }

 platform_set_drvdata(pdev, fbi);
+if (mi->pxa168fb_lcd_power) {
+if (gpio_is_valid(mi->spi_gpio_cs)) {
+ret = gpio_request(mi->spi_gpio_cs, "LCD_SPI_CS");
+if (ret) {
+dev_err(&pdev->dev,
+"failed to request GPIO for LCD CS\n");
+return -EIO;
+}
+}
+ret = mi->pxa168fb_lcd_power(fbi, mi->spi_gpio_cs,
+mi->spi_gpio_reset, 1);
+if (ret) {
+dev_err(&pdev->dev, "Failed to power up pxa168-fb\n");
+goto failed_free_irq;
+}
+}
+dev_info(fbi->de

framebuffer general questions

René Kolařík — 2009-11-13T14:11:48

Hi

i am trying to customize framebuffer drivers and i have some questions...

Please can you give me an advice? 

1) If I define my own imageblit function, how do I call it? Or is it called automatically?

2) I have gpu connected via pci to cpu. I did mmap and have framebuffer mapped in for example "uchar * data". I have loop and iterating through some pixel data and do data[i] = pixel[i]. Does this lead to transmitting via PCI in style - transmit byte ... end ... transmit byte ... end ... etc?

3)what is the difference bethween mmap framebuffer and write to mapped pointer and calling write() to descriptor previously obtained by open()?

these are the main questions in my mind. Thank you for your time i would be glad for any informations.

Rene

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core applicat

[PATCH] mx3fb: adds LCD backlight driver

Anatolij Gustschin — 2009-11-09T11:13:16

To activate this driver select CONFIG_BACKLIGHT_LCD_SUPPORT
in the kernel configuration. Backlight control interface
will be available under /sys/class/backlight/mx3fb/.

Signed-off-by: Anatolij Gustschin <agust< at >denx.de>
---
 drivers/video/mx3fb.c |  100 ++++++++++++++++++++++++++++++++++++++++++++++++-
 1 files changed, 99 insertions(+), 1 deletions(-)

diff --git a/drivers/video/mx3fb.c b/drivers/video/mx3fb.c
index 86312dd..f8f9338 100644
--- a/drivers/video/mx3fb.c
+++ b/drivers/video/mx3fb.c
< at >< at > -30,6 +30,7 < at >< at >
 #include <mach/hardware.h>
 #include <mach/ipu.h>
 #include <mach/mx3fb.h>
+#include <linux/backlight.h>
 
 #include <asm/io.h>
 #include <asm/uaccess.h>
< at >< at > -60,6 +61,12 < at >< at >
 #define SDC_COM_BG_EN0x00000200UL
 #define SDC_COM_SHARP0x00001000UL
 
+#define SDC_PWM_SRC_HSYNC_CLK0x00000000UL
+#define SDC_PWM_SRC_PXL_CLK0x02000000UL
+#define SDC_PWM_SRC_HSP_CLK0x04000000UL
+#define SDC_PWM_CC_EN0x01000000UL
+#define SDC_PWM_PWM_MSK0x00FF0000UL
+
 #define SDC_V_SYNC_WIDTH_L0x00000001UL
 
 /*

[PATCH] mx3fb: Fix display brightnessinitialization

Anatolij Gustschin — 2009-11-09T11:10:07

__blank() uses mx3fb->backlight_level to set the
display brightness. __blank() is also called from
init_fb_chan() before mx3fb->backlight_level was
initialized. This causes setting the display brightness
to zero at probe time.

This patch moves the initialization of mx3fb->backlight_level
before init_fb_chan() call.

Signed-off-by: Anatolij Gustschin <agust< at >denx.de>
---
 drivers/video/mx3fb.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/video/mx3fb.c b/drivers/video/mx3fb.c
index 054ef29..86312dd 100644
--- a/drivers/video/mx3fb.c
+++ b/drivers/video/mx3fb.c
< at >< at > -1486,12 +1486,12 < at >< at > static int mx3fb_probe(struct platform_device *pdev)
 goto ersdc0;
 }
 
+mx3fb->backlight_level = 255;
+
 ret = init_fb_chan(mx3fb, to_idmac_chan(chan));
 if (ret < 0)
 goto eisdc0;
 
-mx3fb->backlight_level = 255;
-
 return 0;
 
 eisdc0:

[PATCH] atmel_lcdfb: silence compiler warningin device info printk

Hans-Christian Egtvedt — 2009-10-29T12:10:34

This patch will tell printk the format for irq_base is a decimal and not an
unsigned long. The irq_base is defined as an int in the struct
atmel_lcdfb_info.

Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt< at >atmel.com>
---
 drivers/video/atmel_lcdfb.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/video/atmel_lcdfb.c b/drivers/video/atmel_lcdfb.c
index 2830ffd..317afab 100644
--- a/drivers/video/atmel_lcdfb.c
+++ b/drivers/video/atmel_lcdfb.c
< at >< at > -959,7 +959,7 < at >< at > static int __init atmel_lcdfb_probe(struct platform_device *pdev)
 if (sinfo->atmel_lcdfb_power_control)
 sinfo->atmel_lcdfb_power_control(1);
 
-dev_info(dev, "fb%d: Atmel LCDC at 0x%08lx (mapped at %p), irq %lu\n",
+dev_info(dev, "fb%d: Atmel LCDC at 0x%08lx (mapped at %p), irq %d\n",
        info->node, info->fix.mmio_start, sinfo->mmio, sinfo->irq_base);
 
 return 0;

[RFC] intelfb + DirectFB + laptop issue

Paulius Zaleckas — 2009-10-29T12:42:41

Hi,

After failing to start DirectFB (tries to get and then set current
resolution) on my asus eeePC I investigated problem and I found out
that it is caused by:

static int intelfb_check_var(struct fb_var_screeninfo *var,
                              struct fb_info *info)
{
...
if (FIXED_MODE(dinfo) &&
    (change_var ||
     var->yres_virtual > dinfo->initial_var.yres_virtual ||
     var->yres_virtual < dinfo->initial_var.yres ||
     var->xoffset || var->nonstd)) {
if (first) {
ERR_MSG("Changing the video mode is not supported.\n");
first = 0;
}
return -EINVAL;
}
...

I my situation FIXED_MODE(dinfo) = true, but change_var = false
It still fails since dinfo->initial_var.yres_virtual is initialized
only once as 0, so var->yres_virtual is always bigger value.

Do we need these checks? chnage_var already does size chekings...

fbset -accel [true|false] also fails because of this check.

Please help me to resolve this issue and we should send patch for stable
also.

BR,
Paulius Zaleckas

--

FBIOPUT_VSCREENINFO: invalid vs. "none" valueof pixclock?

Clemens Ladisch — 2009-10-28T09:51:03

Hi,

what should the pixclock field for the FBIOPUT_VSCREENINFO ioctl be set
to when an application doesn't care about the timing?

The fbset tool and Xorg's fbdevhw driver set it to zero when they have
no timing.  Other programs (like links or xine) set it to the value
returned by FBIOGET_VSCREENINFO.

However, this seems to be different from the actual DRM helpers
implementation:

drm_fb_helper_single_fb_probe() initializes pixclock to -1, and this is
the value returned by FBIOGET_VSCREENINFO.  (Many programs treat this
as a valid value, 0xffffffff = 4 ms.)

drm_fb_helper_check_var() explicitly rejects both values, 0 or -1.

drm_fb_helper_set_par() refuses to work with any value except -1.


Best regards,
Clemens

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
a

[PATCH] offb: add support for framebufferhandoff to offb.

Dave Airlie — 2009-10-27T10:35:28

From: Dave Airlie <airlied< at >redhat.com>

This allows offb to be used for initial framebuffer,
and a kms driver to take over later in the boot sequence.

Signed-off-by: Dave Airlie <airlied< at >redhat.com>
---
 drivers/video/offb.c |   15 ++++++++++++++-
 1 files changed, 14 insertions(+), 1 deletions(-)

diff --git a/drivers/video/offb.c b/drivers/video/offb.c
index 4d8c54c..b043ac8 100644
--- a/drivers/video/offb.c
+++ b/drivers/video/offb.c
< at >< at > -282,8 +282,17 < at >< at > static int offb_set_par(struct fb_info *info)
 return 0;
 }
 
+static void offb_destroy(struct fb_info *info)
+{
+if (info->screen_base)
+iounmap(info->screen_base);
+release_mem_region(info->aperture_base, info->aperture_size);
+framebuffer_release(info);
+}
+
 static struct fb_ops offb_ops = {
 .owner= THIS_MODULE,
+.fb_destroy= offb_destroy,
 .fb_setcolreg= offb_setcolreg,
 .fb_set_par= offb_set_par,
 .fb_blank= offb_blank,
< at >< at > -482,10 +491,14 < at >< at > static void __init offb_init_fb(const char *name, const char *full_name,
 var->sync = 0;

[PATCH] fb: remove fb_save_state() and fb_restore_state operations (bug #11248)

Krzysztof Helt — 2009-10-25T16:00:22

From: Krzysztof Helt <krzysztof.h1< at >wp.pl>

Remove fb_save_state() and fb_restore_state operations from frame buffer layer.
They are used only in two drivers:
1. savagefb  - and cause bug #11248
2. uvesafb

Usage of these operations is misunderstood in both drivers so kill these operations,
fix the bug #11248 and avoid confusion in the future.

Tested on Savage 3D/MV card and the patch fixes the bug #11248.

Signed-off-by: Krzysztof Helt <krzysztof.h1< at >wp.pl>
---
The frame buffer layer uses these funtions during switch between graphics and text 
mode of the console, but these drivers saves state before switching of the frame buffer
(in the fb_open) and after releasing it (in the fb_release). This defeats the purpose of
these operations.

diff --git a/drivers/video/atafb.c b/drivers/video/atafb.c
index 8cd279b..b7687c5 100644
--- a/drivers/video/atafb.c
+++ b/drivers/video/atafb.c
< at >< at > -329,12 +329,6 < at >< at > extern unsigned char fontdata_8x16[];
  *
  ** perform fb specific mmap *
  *int (*fb_mmap)(struct fb_info *i

[PATCH] savagefb: fix blanking mode on CRTdisplay

Krzysztof Helt — 2009-10-25T10:17:04

From: Krzysztof Helt <krzysztof.h1< at >wp.pl>

Fix wrong bit mask for blanking register.  Due to the error a CRT monitor blanks
off due to wrong frequency (out of range) instead of PM signal (vertical and horizontal
frequencies cut off).

Signed-off-by: Krzysztof Helt <krzysztof.h1< at >wp.pl>
---
Just compare the mask with bits set in the switch(blank) clause below the changed line.

diff --git a/drivers/video/savage/savagefb_driver.c b/drivers/video/savage/savagefb_driver.c
index 37b135d..5ad7c79 100644
--- a/drivers/video/savage/savagefb_driver.c
+++ b/drivers/video/savage/savagefb_driver.c
< at >< at > -1565,7 +1565,7 < at >< at > static int savagefb_blank(int blank, struct fb_info *info)
 vga_out8(0x3c5, sr8, par);
 vga_out8(0x3c4, 0x0d, par);
 srd = vga_in8(0x3c5, par);
-srd &= 0x03;
+srd &= 0x50;
 
 switch (blank) {
 case FB_BLANK_UNBLANK:

----------------------------------------------------------------------
Opony do 30% taniej, dostawa gratis!
http://link.interia.pl/f23c9



--------------------------------------

[PATCH] add palette register check

Krzysztof Helt — 2009-10-24T15:18:23

From: Krzysztof Helt <krzysztof.h1< at >wp.pl>

Add check if palette register number is in correct range
for few drivers which miss it. The regno value comes
indirectly from user space.

Two drivers has converted check from BUG_ON() macro
to just return an error (non-zero value).

Signed-off-by: Krzysztof Helt <krzysztof.h1< at >wp.pl>

---

diff --git a/drivers/video/atafb.c b/drivers/video/atafb.c
index 8cd279b..2682938 100644
--- a/drivers/video/atafb.c
+++ b/drivers/video/atafb.c
< at >< at > -2248,6 +2248,9 < at >< at > static int ext_setcolreg(unsigned int regno, unsigned int red,
 if (!external_vgaiobase)
 return 1;
 
+if (regno > 255)
+return 1;
+
 switch (external_card_type) {
 case IS_VGA:
 OUTB(0x3c8, regno);
diff --git a/drivers/video/ep93xx-fb.c b/drivers/video/ep93xx-fb.c
index bd9d46f..27aab4a 100644
--- a/drivers/video/ep93xx-fb.c
+++ b/drivers/video/ep93xx-fb.c
< at >< at > -358,6 +358,8 < at >< at > static int ep93xxfb_setcolreg(unsigned int regno, unsigned int red,
 
 switch (info->fix.visual) {
 case FB_VISUAL_PSEUDOCOLOR:
+

vesafb BIOS interface

Woon Liang Soh — 2009-10-23T02:49:51

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

[PATCH] fbdev: Fix test on unsigned infb_do_show_logo()

Roel Kluin — 2009-10-16T22:45:14

image->d[xy] are unsigned so the check was wrong.

Signed-off-by: Roel Kluin <roel.kluin< at >gmail.com>
---
diff --git a/drivers/video/fbmem.c b/drivers/video/fbmem.c
index 99bbd28..9f20641 100644
--- a/drivers/video/fbmem.c
+++ b/drivers/video/fbmem.c
< at >< at > -403,7 +403,8 < at >< at > static void fb_do_show_logo(struct fb_info *info, struct fb_image *image,
 image->dx += image->width + 8;
 }
 } else if (rotate == FB_ROTATE_UD) {
-for (x = 0; x < num && image->dx >= 0; x++) {
+for (x = 0; x < num && image->dx + image->width + 8 >= 0;
+x++) {
 info->fbops->fb_imageblit(info, image);
 image->dx -= image->width + 8;
 }
< at >< at > -415,7 +416,8 < at >< at > static void fb_do_show_logo(struct fb_info *info, struct fb_image *image,
 image->dy += image->height + 8;
 }
 } else if (rotate == FB_ROTATE_CCW) {
-for (x = 0; x < num && image->dy >= 0; x++) {
+for (x = 0; x < num && image->dy + image->height + 8 >= 0;
+x++) {
 info->fbops->fb_imageblit(info, image);
 image->dy -= image->height + 8;
 }

-----------