- 10 Jan, 2006 40 commits
-
-
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:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Antonino A. Daplas authored
Update skeletonfb so it reflects recent (and somewhat old) changes of the framebuffer layer. Signed-off-by:
Antonino Daplas <adaplas@pol.net> 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ä <syrjala@sci.fi> 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:
-
Antonino A. Daplas authored
- remove unneeded casts - use framebuffer_alloc/framebuffer_release to allocate/free memory - the pseudo_palette is always u32 regardless of bpp if using generic drawing functions Signed-off-by:
Paul Mundt <lethal@linux-sh.org> Signed-off-by:
-
Antonino A. Daplas authored
- remove unneeded casts - the pseudo_palette, if using the generic drawing functions, must always be u32 regardless of the bpp - use framebuffer_alloc/framebuffer_release to allocate memory Signed-off-by:
-
Antonino A. Daplas authored
- convert to platform device Signed-off-by:
-
Antonino A. Daplas authored
- allocate just enough space for the pseudo_palette Signed-off-by:
-
Antonino A. Daplas authored
- remove redundant casts Signed-off-by:
-
Antonino A. Daplas authored
- remove redundant casts Signed-off-by:
-
Antonino A. Daplas authored
- remove redundant casts - remove symbol_get/symbol_put Signed-off-by:
-
Antonino A. Daplas authored
- remove redundant casts - add mode_option to module parameter Signed-off-by:
-
Matthew Garrett authored
What
-
Jean Delvare authored
The I2C bus of the S3 Savage2000 is supposed to work the same way the Savage4 does. At least, the legacy i2c-savage4 driver handled both devices the same way. I do not have the hardware to test this, so testers are welcome. Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Antonino A. Daplas authored
matroxfb has no need for struct display and fbcon.h. Remove. Signed-off-by:
-
Antonino A. Daplas authored
Store struct display when setting all vc's. Otherwise, fbcon's behavior becomes undefined, such as malpositioning of the cursor. Signed-off-by:
-
Alessandro Zummo authored
Assign nvidiafb's i2c busses a better name. Signed-off-by:
Alessandro Zummo <a.zummo@towertech.it> Signed-off-by:
-
Antonino A. Daplas authored
Do not pass the structure display since fbcon is already keeping the pointer to the current display. Signed-off-by:
-
Richard Knutsson authored
Signed-off-by:
Richard Knutsson <ricknu-0@student.ltu.se> Cc: "Antonino A. Daplas" <adaplas@pol.net> Signed-off-by:
-
Antonino A. Daplas authored
From: Bugzilla Bug 5351 "After resuming from S3 (suspended while in X), the LCD panel stays black . However, the laptop is up again, and I can SSH into it from another machine. I can get the panel working again, when I first direct video output to the CRT output of the laptop, and then back to LCD (done by repeatedly hitting Fn+F5 buttons on the Toshiba, which directs output to either LCD, CRT or TV) None of this ever happened with older kernels." This bug is due to the recently added vesafb_blank() method in vesafb. It works with CRT displays, but has a high incidence of problems in laptop users. Since CRT users don't really get that much benefit from hardware blanking, drop support for this. Signed-off-by:
-
