Skip to content
Snippets Groups Projects
  1. Apr 30, 2011
  2. Apr 29, 2011
  3. Apr 28, 2011
    • Wolfgang Denk's avatar
    • Wolfgang Denk's avatar
      34d9cb5e
    • Timur Tabi's avatar
      powerpc: use 'video-mode' environment variable to configure DIU · ba8e76bd
      Timur Tabi authored
      
      Use the 'video-mode' environment variable (for Freescale chips that have a
      DIU display controller) to designate the full video configuration.  Previously,
      the DIU driver used the 'monitor' variable, and it was used only to determine
      the output video port.
      
      The old definition of the "monitor" environment variable only determines
      which video port to use for output.  This variable was set to a number (0,
      1, or sometimes 2) to specify a DVI, LVDS, or Dual-LVDS port.  The
      resolution was hard-coded into board-specific code.  The Linux command-line
      arguments needed to be hard-coded to the proper video definition string.
      
      Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
      Signed-off-by: default avatarAnatolij Gustschin <agust@denx.de>
      ba8e76bd
    • Timur Tabi's avatar
      video: parse the video-mode environment variable · a5dbdc81
      Timur Tabi authored
      
      Add function video_get_video_mode(), which parses the "video-mode" environment
      variable and returns each of its components.  The format matches the video=
      command-line option used for Linux:
      
      	video-mode=<driver>:<xres>x<yres>-<depth>@<freq><,option=string>
      
      	<driver> The video driver, ignored by U-Boot
      	<xres> The X resolution (in pixels) to use.
      	<yres> The Y resolution (in pixels) to use.
      	<depth> The color depth (in bits) to use.
      	<freq> The frequency (in Hz) to use.
      	<options> A comma-separated list of device-specific options
      
      Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
      a5dbdc81
    • Anatolij Gustschin's avatar
      cfb_console: fix RLE bitmap drawing code · 74446b63
      Anatolij Gustschin authored
      
      There seems to be tools producing incorrect 'end of bitmap data'
      markers '0100' in a RLE bitmap. Drawing such bitmaps can result
      in overwriting memory above the frame buffer. E.g. on MPC5121e
      based boards this memory can contain U-Boot environment.
      
      We may not rely on the correct end of bitmap data marker 0001
      only, but also have to check whether we are going to draw a
      valid frame buffer scan line.
      
      The patch provides a fix by maintaining a pixel counter
      which is incremented by the amount of pixels we are going
      to draw. If the counter exceeds frame buffer pixels limit
      we stop the drawing with the error message.
      
      Reported-by: default avatarMichael Weiss <michael.weiss@ifm.com>
      Signed-off-by: default avatarAnatolij Gustschin <agust@denx.de>
      Tested-by: default avatarAnatolij Gustschin <agust@denx.de>
      74446b63
Loading