- 10 Jan, 2006 40 commits
-
-
Martin Waitz authored
Fix typos in comments to remove kernel-doc warnings. Signed-off-by:
Martin Waitz <tali@admingilde.org> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Martin Waitz authored
Signed-off-by:
-
Martin Waitz authored
when ignoring all DocBook output files git-status output becomes meaningful again. Signed-off-by:
-
Jesper Juhl authored
Signed-off-by:
Jesper Juhl <jesper.juhl@gmail.com> Signed-off-by:
-
Ville Syrjala authored
Current console blanking code is broken. It will first do a normal blank, then start the VESA blank timer if vesa_off_interval != 0, and then proceed to do the VESA blanking directly. After the timer expires it will do the VESA blanking a second time. Also the vesa_powerdown() function doesn't allow all VESA modes to be used. With this patch the behaviour is: 1. Blank: vesa_off_interval != 0 -> Do normal blank vesa_off_interval == 0 -> Do VESA blank 2. Start the VESA blank timer if vesa_off_interval != 0 and vesa_power_mode != 0. It also gets rid of the limiting vesa_powerdown() function. Signed-off-by:Ville Syrjala <syrjala@sci.fi> Cc: "Antonino A. Daplas" <adaplas@pol.net> Signed-off-by:
-
Thomas Koeller authored
While the code in fbmem.c allows for hooking read/write access to non-linear frame buffers by means of fb_read and fb_write in struct fb_ops, I could not find a way tho access the actual frame buffer memory from within these routines. I therefore had to patch fbmem.c, to be able to retrieve a pointer to struct fb_info from the 'file' argument to these functions. The second hunk of the patch is not strictly required, I only did that for symmetry reasons (and the code is somewhat shorter). Signed-off-by:
Thomas Koeller <thomas@koeller.dyndns.org> Acked-by:
"Antonino A. Daplas" <adaplas@gmail.com> Signed-off-by:
-
YOSHIFUJI Hideaki authored
Signed-off-by:
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org> Cc: "Antonino A. Daplas" <adaplas@pol.net> Signed-off-by:
-
Antonino A. Daplas authored
Replace kmalloc with kzalloc Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino A. Daplas authored
- replace kmalloc with kzalloc - remove repeated define (FONTCHHCNT) - remove unneeded local variable (redraw) in ypan_{up|down}_redraw - add and delete cursor timer in fbcon_switch() if old_info != info Signed-off-by: -
Antonino A. Daplas authored
The i810fb suspend and resume hooks have suffered bitrot over time. Update to current framework, but functionality still not guaranteed to work. Signed-off-by:
-
Arnaud Patard authored
Here are some cleanups for the s3c2410fb drivers. It : * Removes a buggy call to s3c2410fb_init_registers. There was two calls to this function but the first was done without all initialisations done. No oops but it may confuse some LCDs. * Makes two functions static. Signed-Off-By:
Arnaud Patard <arnaud.patard@rtp-net.org> Signed-Off-By:
-
Antonino A. Daplas authored
Reduce stack usage of NVCommonSetup() Signed-off-by:
-
Antonino A. Daplas authored
Add boot/module option 'bpp' so user can specify at what color depth to boot into. Signed-off-by:
-
Antonino A. Daplas authored
calc_mode_timings() and fb_get_mode() are using more than 500 bytes off the stack. Fix. Signed-off-by:
-
Antonino A. Daplas authored
Make fb_read() and fb_write() return 0 (EOF) instead of -ENOSPC if reading at or past the end of the framebuffer. This fixes user space apps hanging if info->fix.smem_len == 0. Whitespace changes. Signed-off-by:
-
Knut Petersen authored
updatescrollmode() must not select ywrap scrolling if divides(vc->vc_font.height, yres) is not true as this is not supported by the actual ywrap scrolling code. The bug is triggered with e.g. mode 800x600, vxres 1024, vyres 8192, bpp 8, font dimensions 8x16, 8Mb video ram and FBINFO_HWACCEL_YWRAP set. If those conditions are met, scrolling is broken and garbage is permanently displayed at the bottom of the screen. No regression, no possible side effects. Definitely needed by cyblafb and probably needed by amifb. Signed-off-by:
Knut Petersen <Knut_Petersen@t-online.de> Acked-by:
-
Adrian Bunk authored
"extern inline" doesn't make much sense. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Cc: "Antonino A. Daplas" <adaplas@pol.net> Signed-off-by:
-
Antonino A. Daplas authored
Update skeletonfb so it reflects recent (and somewhat old) changes of the framebuffer layer. Signed-off-by:
-
Antonino A. Daplas authored
Chipsets with PCI device ids & 0xf0 == 0x00f0 has their actual chipset type in offset 0x1800 of the mmio space. Add support for this. Signed-off-by:
-
Ville Syrjälä authored
Clean up LT and LG chip descriptions. "Mach64 LG" is called 3D Rage LT in the specs and ATI press releases. "Mach64 LT" is unclear. XFree86 driver doesn't know this chip at all. Windows display.inf calls it just "mach64 LT" and it uses the same driver as VT-A/GT-A and older chips. VT-B/GT-B and better use another driver and all of those chips have a more descriptive name in the display.inf file. That makes me think this chip is not a 3D Rage chip. Signed-off-by:
-
Ville Syrjälä authored
Clean up VT and GT chip descriptions. All B revision VT chips are called 264VT3. Verified from pictures of the chips as the specs are a bit unlear in this. GT revision B1 is Rage II, B2 is Rage II+. Specs and chip pictures seem to agree. VT revision A4 is 264VT2. Revision A3 is probably a plain 264VT. Signed-off-by:
-
Ville Syrjälä authored
Clean up Rage XL/XC chip descriptions. Signed-off-by:
-
Ville Syrjälä authored
Force blanking signal and disable display requests when blanked. Don't disable LCD backlight with FB_BLANK_NORMAL. Signed-off-by:
-
Ville Syrjälä authored
Set ECP (scaler/overlay clock) divider. The limits were taken from the XFree86 ati driver. Signed-off-by:
-
Ville Syrjälä authored
The overlay on 3D Rage LT Pro doesn't work correctly if stretching is enabled when using only a CRT. Signed-off-by:
-
Ville Syrjälä authored
Fix interlaced display modes. Signed-off-by:
-
Ville Syrjälä authored
CRTC_FIFO_LWM was incorrectly masked. Signed-off-by:
-
Ville Syrjälä authored
Don't complain about invalid modes when FB_ACTIVATE_TEST is used. Signed-off-by:
-
Ville Syrjälä authored
Fix some spelling mistakes. Signed-off-by:
-
Antonino A. Daplas authored
Remove error checking and updating from vga16fb_pan_display. This is guaranteed to be done by the core layer. Signed-off-by:
-
Antonino A. Daplas authored
Fix vesafb hang when scroll mode is REDRAW. Signed-off-by:
-
Antonino A. Daplas authored
Remove error checking from vesafb_pan_display. This is guaranteed to be done by the core layer. Signed-off-by:
-
Antonino A. Daplas authored
Remove error checking and updating from savagefb_pan_display. This is guaranteed to be done by the core layer. Signed-off-by:
-
Antonino A. Daplas authored
Remove error checking and updating from rivafb_pan_display. This is guaranteed to be done by the core layer. Signed-off-by:
-
Antonino A. Daplas authored
- remove unneeded casts - make setcolreg return success if regno > 15, but don't do anything - use framebuffer_alloc/framebuffer_release to allocate/free memory Signed-off-by:
-
Antonino A. Daplas authored
CONFIG_ATYFB_XL_INIT option is broken for a long time. It will always cause a kernel hang. Since no one has fixed this problem for some time now, remove it from atyfb. Signed-off-by:
-
Antonino A. Daplas authored
- remove unneeded casts Signed-off-by:
-
Antonino A. Daplas authored
- remove unneeded casts - move memory for pseudo_palette inside struct tdfxfb_par - whitespace changes Signed-off-by:
-
Antonino A. Daplas authored
- remove unneeded casts - move memory for pseudo_palette inside struct pm2fb_par Signed-off-by:
-
Antonino A. Daplas authored
- remove unneeded casts - move memory for pseudo_palette inside struct neofb_par Signed-off-by:
-
