Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 161
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 03 4月, 2014 1 次提交
  3. 19 3月, 2014 1 次提交
  5. 17 3月, 2014 1 次提交
  7. 12 3月, 2014 1 次提交
  9. 07 3月, 2014 7 次提交
  11. 06 3月, 2014 2 次提交
  13. 05 3月, 2014 2 次提交
  15. 28 2月, 2014 8 次提交
  17. 14 2月, 2014 2 次提交
  19. 11 2月, 2014 13 次提交
    • M
      video: xilinxfb: Move xilinxfb_platform_data directly to the driver · c4a41bcc
      由 Michal Simek 提交于 
      No reason to have separate file in header in include/linux folder
if this is purely driver specific structure.
Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      c4a41bcc
    • A
      video: imxfb: Use regulator API with LCD class for powering · 9fe21fdc
      由 Alexander Shiyan 提交于 
      This patch replaces custom lcd_power() callback with
regulator API over LCD class.
Signed-off-by: NAlexander Shiyan <shc_work@mail.ru>
Acked-by: NShawn Guo <shawn.guo@linaro.org>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      9fe21fdc
    • M
      tgafb: avoid restriction on modes with line length not a multiple of 64 · e62cabb5
      由 Mikulas Patocka 提交于 
      In tgafb there is a restriction that prevents the user from setting a
videomode with line length not a multiple of 64 bytes (for example,
800x600 is not allowed).

The reason for this restriction it that functions copyarea_line_8bpp and
copyarea_line_32bpp can not handle a line length that is not a multiple
of 64 bytes.

This patch removes this restriction on mode setting and makes sure that
the functions copyarea_line_8bpp and copyarea_line_32bpp are called only
if line length is a multiple of 64 bytes. If we set a mode 800x600,
the functions copyarea_line_8bpp and copyarea_line_32bpp are not used,
generic functions for copying are used instead and it works just fine.
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      e62cabb5
    • M
      tgafb: fix data copying · 6b0df682
      由 Mikulas Patocka 提交于 
      The functions for data copying copyarea_foreward_8bpp and
copyarea_backward_8bpp are buggy, they produce screen corruption.

This patch fixes the functions and moves the logic to one function
"copyarea_8bpp". For simplicity, the function only handles copying that
is aligned on 8 pixes. If we copy an unaligned area, generic function
cfb_copyarea is used.
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      6b0df682
    • M
      tgafb: fix mode setting with fbset · 62496658
      由 Mikulas Patocka 提交于 
      Mode setting in the TGA driver is broken for these reasons:

- info->fix.line_length is set just once in tgafb_init_fix function. If
  we change videomode, info->fix.line_length is not recalculated - so
  the video mode is changed but the screen is corrupted because of wrong
  info->fix.line_length.

- info->fix.smem_len is set in tgafb_init_fix to the size of the default
  video mode (640x480). If we set a higher resolution,
  info->fix.smem_len is smaller than the current screen size, preventing
  the userspace program from mapping the framebuffer.

This patch fixes it:

- info->fix.line_length initialization is moved to tgafb_set_par so that
  it is recalculated with each mode change.

- info->fix.smem_len is set to a fixed value representing the real
  amount of video ram (the values are taken from xfree86 driver).

- add a check to tgafb_check_var to prevent us from setting a videomode
  that doesn't fit into videoram.

- in tgafb_register, tgafb_init_fix is moved upwards, to be called
  before fb_find_mode (because fb_find_mode already needs the videoram
  size set in tgafb_init_fix).
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Cc: stable@vga.kernel.org
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      62496658
    • M
      mach64: fix cursor when character width is not a multiple of 8 pixels · 43751a1b
      由 Mikulas Patocka 提交于 
      This patch fixes the hardware cursor on mach64 when font width is not a
multiple of 8 pixels.

If you load such a font, the cursor is expanded to the next 8-byte
boundary and a part of the next character after the cursor is not
visible.
For example, when you load a font with 12-pixel width, the cursor width
is 16 pixels and when the cursor is displayed, 4 pixels of the next
character are not visible.

The reason is this: atyfb_cursor is called with proper parameters to
load an image that is 12-pixel wide. However, the number is aligned on
the next 8-pixel boundary on the line
"unsigned int width = (cursor->image.width + 7) >> 3;" and the whole
function acts as it is was loading a 16-pixel image.

This patch fixes it so that the value written to the framebuffer is
padded with 0xaaaa (the transparent pattern) when the image size it not
a multiple of 8 pixels. The transparent pattern causes that the cursor
will not interfere with the next character.
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      43751a1b
    • M
      atyfb: set FBINFO_READS_FAST · c38882e3
      由 Mikulas Patocka 提交于 
      Set FBINFO_READS_FAST so that the console code uses scrolling instead of
rewriting. This improves scrolling speed.

A time to do ls -la /usr/bin:
	original patched
32bpp	4.9	3.6
24bpp	4.9	2.9
16bpp	4.9	2.1
8bpp	4.9	1.7
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      c38882e3
    • M
      mach64: use unaligned access · c29dd869
      由 Mikulas Patocka 提交于 
      This patch fixes mach64 to use unaligned access to the font bitmap.

This fixes unaligned access warning on sparc64 when 14x8 font is loaded.

On x86(64), unaligned access is handled in hardware, so both functions
le32_to_cpup and get_unaligned_le32 perform the same operation.

On RISC machines, unaligned access is not handled in hardware, so we
better use get_unaligned_le32 to avoid the unaligned trap and warning.
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      c29dd869
    • M
      atyfb: remove resolution limit 1600 · bf26e6d2
      由 Mikulas Patocka 提交于 
      The card works fine in 1980x1080 resolution. Therefore, there is no need
to limit the resolution to 1600 pixels.
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      bf26e6d2
    • M
      framebuffer: fix cfb_copyarea · 00a9d699
      由 Mikulas Patocka 提交于 
      The function cfb_copyarea is buggy when the copy operation is not aligned on
long boundary (4 bytes on 32-bit machines, 8 bytes on 64-bit machines).

How to reproduce:
- use x86-64 machine
- use a framebuffer driver without acceleration (for example uvesafb)
- set the framebuffer to 8-bit depth
	(for example fbset -a 1024x768-60 -depth 8)
- load a font with character width that is not a multiple of 8 pixels
	note: the console-tools package cannot load a font that has
	width different from 8 pixels. You need to install the packages
	"kbd" and "console-terminus" and use the program "setfont" to
	set font width (for example: setfont Uni2-Terminus20x10)
- move some text left and right on the bash command line and you get a
	screen corruption

To expose more bugs, put this line to the end of uvesafb_init_info:
info->flags |= FBINFO_HWACCEL_COPYAREA | FBINFO_READS_FAST;
- Now framebuffer console will use cfb_copyarea for console scrolling.
You get a screen corruption when console is scrolled.

This patch is a rewrite of cfb_copyarea. It fixes the bugs, with this
patch, console scrolling in 8-bit depth with a font width that is not a
multiple of 8 pixels works fine.

The cfb_copyarea code was very buggy and it looks like it was written
and never tried with non-8-pixel font.
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      00a9d699
    • M
      matroxfb: restore the registers M_ACCESS and M_PITCH · a772d473
      由 Mikulas Patocka 提交于 
      When X11 is running and the user switches back to console, the card
modifies the content of registers M_MACCESS and M_PITCH in periodic
intervals.

This patch fixes it by restoring the content of these registers before
issuing any accelerator command.
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      a772d473
    • M
      matroxfb: set FBINFO_READS_FAST · a2317e6a
      由 Mikulas Patocka 提交于 
      Set FBINFO_READS_FAST so that the console code uses scrolling instead of
rewriting. This improves scrolling speed.

A time to do ls -la /usr/bin:
	original patched
32bpp	5.4	3.6
24bpp	5.1	3.0
16bpp	4.9	2.5
8bpp	4.9	2.0
Signed-off-by: NMikulas Patocka <mpatocka@redhat.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      a2317e6a
    • K
      fbcon: Clean up fbcon data in fb_info on FB_EVENT_FB_UNBIND with 0 fbs · 5f4dc28b
      由 Keith Packard 提交于 
      When FB_EVENT_FB_UNBIND is sent, fbcon has two paths, one path taken
when there is another frame buffer to switch any affected vcs to and
another path when there isn't.

In the case where there is another frame buffer to use,
fbcon_fb_unbind calls set_con2fb_map to remap all of the affected vcs
to the replacement frame buffer. set_con2fb_map will eventually call
con2fb_release_oldinfo when the last vcs gets unmapped from the old
frame buffer.

con2fb_release_oldinfo frees the fbcon data that is hooked off of the
fb_info structure, including the cursor timer.

In the case where there isn't another frame buffer to use,
fbcon_fb_unbind simply calls fbcon_unbind, which doesn't clear the
con2fb_map or free the fbcon data hooked from the fb_info
structure. In particular, it doesn't stop the cursor blink timer. When
the fb_info structure is then freed, we end up with a timer queue
pointing into freed memory and "bad things" start happening.

This patch first changes con2fb_release_oldinfo so that it can take a
NULL pointer for the new frame buffer, but still does all of the
deallocation and cursor timer cleanup.

Finally, the patch tries to replicate some of what set_con2fb_map does
by clearing the con2fb_map for the affected vcs and calling the
modified con2fb_release_info function to clean up the fb_info structure.
Signed-off-by: NKeith Packard <keithp@keithp.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      5f4dc28b
  21. 10 2月, 2014 2 次提交