17 Oct, 2007

2 commits

  • The i.MX frame-buffer read operation should be faster for all configurations
    then drawing each individual character again in response to scroll events.

    The nonstandard fields allows to configure frame-buffer special options flags
    for different display configurations by board specific initialization code.

    One of such specific options is reversed order of pixels in each individual
    byte. i.MX frame-buffer seems to be designed for big-endian use first. The
    byte order is correctly configured for little-endian ordering, but if 1, 2 or
    4 bits per pixel are used, pixels ordering is incompatible to Linux generic
    frame-buffer drawing functions.

    The patch "Allow generic BitBLT functions to work with swapped pixel order in
    bytes" introduces required functionality into FBDEV core. The pixels ordering
    selection has to be enabled at compile time CONFIG_FB_CFB_REV_PIXELS_IN_BYTE
    and for each display configuration which requires it by flag
    FB_NONSTD_REV_PIX_IN_B in "nonstd" field of info structure.

    This patch provides way for board specific code to select this option.

    Signed-off-by: Pavel Pisa
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Pisa
     
  • This patch replaces with after the
    checkpatch.pl hint. The include of is removed if the driver
    does not use it.

    Signed-off-by: Krzysztof Helt
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Krzysztof Helt
     

24 May, 2007

2 commits

  • info->pseudo_palette was previously kmalloced. Do not overwrite it afterwards

    Signed-off-by: Sascha Hauer
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Sascha Hauer
     
  • Here are some small fixes for the imxfb framebuffer driver:

    - remove ifndef for MX1FS2 platform which is not present in the kernel.
    - REV, CLS, PS and SPL_SPR are only needed with some sharp displays.
    Only setup the corresponding io pins when such a display is connected.

    Signed-off-by: Sascha Hauer
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Sascha Hauer
     

15 Feb, 2007

1 commit

  • After Al Viro (finally) succeeded in removing the sched.h #include in module.h
    recently, it makes sense again to remove other superfluous sched.h includes.
    There are quite a lot of files which include it but don't actually need
    anything defined in there. Presumably these includes were once needed for
    macros that used to live in sched.h, but moved to other header files in the
    course of cleaning it up.

    To ease the pain, this time I did not fiddle with any header files and only
    removed #includes from .c-files, which tend to cause less trouble.

    Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
    arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
    allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
    configs in arch/arm/configs on arm. I also checked that no new warnings were
    introduced by the patch (actually, some warnings are removed that were emitted
    by unnecessarily included header files).

    Signed-off-by: Tim Schmielau
    Acked-by: Russell King
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Tim Schmielau
     

01 Jul, 2006

1 commit


07 Jan, 2006

1 commit


10 Nov, 2005

1 commit


07 Nov, 2005

1 commit

  • According to Jon Smirl, filling in the field fb_cursor with soft_cursor for
    drivers that do not support hardware cursors is redundant. The soft_cursor
    function is usable by all drivers because it is just a wrapper around
    fb_imageblit. And because soft_cursor is an fbcon-specific hook, the file is
    moved to the console directory.

    Thus, drivers that do not support hardware cursors can leave the fb_cursor
    field blank. For drivers that do, they can fill up this field with their own
    version.

    The end result is a smaller code size. And if the framebuffer console is not
    loaded, module/kernel size is also reduced because the soft_cursor module will
    also not be loaded.

    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Antonino A. Daplas
     

30 Oct, 2005

1 commit


29 Oct, 2005

1 commit

  • In PM v1, all devices were called at SUSPEND_DISABLE level. Then
    all devices were called at SUSPEND_SAVE_STATE level, and finally
    SUSPEND_POWER_DOWN level. However, with PM v2, to maintain
    compatibility for platform devices, I arranged for the PM v2
    suspend/resume callbacks to call the old PM v1 suspend/resume
    callbacks three times with each level in order so that existing
    drivers continued to work.

    Since this is obsolete infrastructure which is no longer necessary,
    we can remove it. Here's an (untested) patch to do exactly that.

    Signed-off-by: Russell King
    Signed-off-by: Greg Kroah-Hartman

    Russell King
     

29 Sep, 2005

1 commit


18 Sep, 2005

1 commit


18 Jul, 2005

1 commit


01 May, 2005

1 commit

  • This patch adds support for the framebuffer on the freescale i.MX SOC
    architecture. The driver has been tested on the mx1ads board, the pimx1 board
    and another custom board with different displays.

    Signed-off-by: Sascha Hauer
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Sascha Hauer