- 08 May, 2007 40 commits
-
-
Antonino A. Daplas authored
Check if the mode can properly display the screen. This will be needed by drivers where the capability is not constant with each mode. The function fb_set_var() will query fbcon the requirement, then it will query the driver (via a new hook fb_get_caps()) its capability. If the driver's capability cannot handle fbcon's requirement, then fb_set_var() will fail. For example, if a particular driver supports 2 modes where: mode1 = can only display 8x16 bitmaps mode2 = can display any bitmap then if current mode = mode2 and current font = 12x22 fbset <mode1> /* mode1 cannot handle 12x22 */ fbset will fail Signed-off-by:
Antonino Daplas <adaplas@gmail.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
Dave Jones authored
If the chip locks up, we get into a long polling loop, where the softlockup detector kicks in. See https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=151878 for an example. [adaplas] Chip lockup can occur at 3 points (flush, sync, and wait). Consolidate and allow the driver to go to safe mode cleanly. Signed-off-by:
Dave Jones <davej@redhat.com> Signed-off-by:
-
Krzysztof Helt authored
This patch adds restrictions to calculations of m, n and p factors which sets the pixclock for the Permedia 2V. I found during tests that synchronization is unstable if m (divisor) is bigger than half of the n (numerator). The patch disallows such settings combination. Signed-off-by:
Krzysztof Helt <krzysztof.h1@wp.pl> Signed-off-by:
-
Krzysztof Helt authored
Permedia 2V uses its own registers to set a memory clock. The patch adds these registers and uses them in the set_memclock() function. Signed-off-by:
-
Krzysztof Helt authored
This patch adds support for 3dlabs Permedia reference board. Signed-off-by:
-
Alan Cox authored
Switch to pci_get refcounting APIs [adaplas] Fix a long-standing bug where the return value of pci_find_slot()/pci_get_bus_and_slot() is ignored. Signed-off-by:
Alan Cox <alan@redhat.com> Signed-off-by:
-
Alan Hourihane authored
Add the Intel Vermilion Range framebuffer support. Signed-off-by:
Alan Hourihane <alanh@tungstengraphics.com> Signed-off-by:
-
Ondrej Zajicek authored
This fixes broken fbcon on Virge VX in 24 bpp mode, and contains several other small updates. Signed-off-by:
Ondrej Zajicek <santiago@crfreenet.org> Signed-off-by:
-
Antonino A. Daplas authored
Some drivers may reset the var->activate field on fb_check_var(). This can lead to undefined behavior. For example, doing fbset -a <option> with vga16fb will only modify the active console instead of modifying all. Signed-off-by:
-
Antonino A. Daplas authored
Fontmaps can be 256 or 512 in length. The only driver that can do tileblitting can only handle 256 characters. Check for this when setting the font. Signed-off-by:
-
Antonino A. Daplas authored
Implement fb_get_tilemax(). It just returns 256. Signed-off-by:
-
Antonino A. Daplas authored
Add a tile method, fb_get_tilemax(), that returns the maximum length of the tile map (or font map). This is needed by s3fb which can only handle 256 characters. Signed-off-by:
-
Antonino A. Daplas authored
If tileblitting is enabled (text mode), the hardware can only accept 8x16 bitmaps. Advertise this to the upper layer. And to ensure that an appropriate font is always available, select an 8x16 font in Kconfig. Signed-off-by:
-
Antonino A. Daplas authored
Advertise that vga16fb can only handle widths that are 8-pixel-multiple only (software limitation). To ensure that a legal font is available, SELECT an 8x16 font in Kconfig. Signed-off-by:
-
Antonino A. Daplas authored
fbcon_set_font() will now check if the new font dimensions can be drawn by the driver (by checking pixmap.blit_x and blit_y). Similarly, add 2 new parameters to get_default_font(), font_w and font_h, to further aid in the font selection process. Signed-off-by:
-
Antonino A. Daplas authored
A few drivers are not capable of blitting rectangles of any dimension. vga16fb can only blit 8-pixel wide rectangles, while s3fb (in tileblitting mode) can only blit 8x16 rectangles. For example, loading a 12x22 font in vga16fb will result in a corrupt display. Advertise this limitation/capability in info->pixmap.blit_x and blit_y. These fields are 32-bit arrays (font max is 32x32 only), ie, if bit 7 is set, then width/height of 7+1 is supported. Signed-off-by:
-
Antonino A. Daplas authored
Consolidate common drawing functions into a single header file. Signed-off-by:
-
Antonino A. Daplas authored
Since vfb's framebuffer is vmalloc'ed, use the fb_sys_read() and fb_sys_write(). Signed-off-by:
-
Antonino A. Daplas authored
Since hecubafb's framebuffer is vmalloc'ed, use fb_sys_read(). Signed-off-by:
-
Antonino A. Daplas authored
Since arcfb's framebuffer is vmalloc'ed, use the fb_sys_read(). Signed-off-by:
-
Antonino A. Daplas authored
The functions fb_read() and fb_write in fbmem.c assume that the framebuffer is in IO memory. However, we have 3 drivers (hecubafb, arcfb, and vfb) where the framebuffer is allocated from system RAM (via vmalloc). Using __raw_read/__raw_write (fb_readl/fb_writel) for these drivers is illegal, especially in other platforms. Create file read and write methods for these types of drivers. These are named fb_sys_read() and fb_sys_write(). Signed-off-by:
-
Antonino A. Daplas authored
It is unnecessary to pass struct file to fb_read() and fb_write() in struct fb_ops. For consistency with the other methods, pass struct fb_info instead. Signed-off-by:
Paul Mundt <lethal@linux-sh.org> Signed-off-by:
-
Antonino A. Daplas authored
Since vfb's framebuffer is vmalloc'ed, use the sys_* drawing functions instead of cfb_*. Signed-off-by:
-
Antonino A. Daplas authored
Since hecubafb's framebuffer is vmalloc'ed, use the sys_* drawing functions instead of cfb_*. Signed-off-by:
-
Antonino A. Daplas authored
Since arcfb's framebuffer is vmalloc'ed, use the sys_* drawing functions instead of cfb_*. Signed-off-by:
-
Antonino A. Daplas authored
The generic drawing functions (cfbimgblt, cfbcopyarea, cfbfillrect) assume that the framebuffer is in IO memory. However, we have 3 drivers (hecubafb, arcfb, and vfb) where the framebuffer is allocated from system RAM (via vmalloc). Using _raw_read/write and family for these drivers (as used in the cfb* functions) is illegal, especially in other platforms. Create 3 new drawing functions, based almost entirely from the original except that the framebuffer memory is assumed to be in system RAM. These are named as sysimgblt, syscopyarea, and sysfillrect. Signed-off-by:
-
Antonino A. Daplas authored
Documentation error fixes. Signed-off-by:
-
Antonino A. Daplas authored
Add description to Documentation/kernel-parameters.txt on new options default_blue, default_grn, default_red, and default_utf8. Signed-off-by:
-
Antonino A. Daplas authored
Fix a long-standing bug. The mask used to detect a 100Mhz or 133Mhz chipset is incorrect. (The only side effect of this bug is that it will choose an incorrect watermark). Signed-off-by:
-
Antonino A. Daplas authored
The framebuffer memory is allocated from system RAM (vmalloc'ed). Add __force annotations. Signed-off-by:
-
Antonino A. Daplas authored
Add sparse annotations and use fb_read/fb_write and family to access the framebuffer. Signed-off-by:
-
Antonino A. Daplas authored
The framebuffer memory is allocated from system RAM (vmalloc'ed). Add __force annotations. Signed-off-by:
-
Antonino A. Daplas authored
Add sparse annotations and use fb_read/fb_write family to access the framebuffer. Signed-off-by:
-
Antonino A. Daplas authored
Kill the following in fb_defio.c: drivers/video/fb_defio.c:40:43: warning: incorrect type in argument 1 (different address spaces) drivers/video/fb_defio.c:40:43: expected void *addr drivers/video/fb_defio.c:40:43: got char [noderef] *screen_base<asn:2> The framebuffer memory of these types of devices are allocated from system RAM. Signed-off-by:
-
Antonino A. Daplas authored
Fix IO access, with the following sparse warnings: drivers/video/riva/fbdev.c:320:25: warning: dereference of noderef expression drivers/video/riva/fbdev.c:321:29: warning: dereference of noderef expression drivers/video/riva/fbdev.c:327:18: warning: dereference of noderef expression drivers/video/riva/fbdev.c:328:15: warning: dereference of noderef expression Signed-off-by:
-
Antonino A. Daplas authored
Fix the following sparse warning: drivers/video/nvidia/nv_setup.c:659:20: warning: dereference of noderef expression Signed-off-by:
-
Antonino A. Daplas authored
If the current framebuffer console is rotated (rotate != 0), doing an "fbset -a" will corrupt the current console. Fix by updating the current console only after all non-visible consoles have been updated. Signed-off-by:
-
Antonino A. Daplas authored
Instead of directly linking vgastate.o by individual drivers, create a Kconfig option VGASTATE which can be 'SELECT'ed by individual drivers instead. Signed-off-by:
-
Antonino A. Daplas authored
Allow the saving and restoration of VGA text mode. The state is saved on the first open and restored on the last close. Because of the VGA registers are linearly mapped to the MMIO space, MMIO access is used which is not limited to X86 platforms nor to the primary display device. An echo 0 > /sys/class/vtconsole/vtcon1/bind will convert the display from graphics to text mode. Signed-off-by:
-
Antonino A. Daplas authored
Use already defined VGAwCR/VGArCR functions to access the i2c bus. Signed-off-by:
-
