# This is a BitKeeper generated diff -Nru style patch. diff -Nru a/Documentation/fb/vesafb.txt b/Documentation/fb/vesafb.txt --- a/Documentation/fb/vesafb.txt 2005-03-28 23:14:56 +02:00 +++ b/Documentation/fb/vesafb.txt 2005-03-28 23:14:56 +02:00 @@ -2,16 +2,18 @@ What is vesafb? =============== -This is a generic driver for a graphic framebuffer on intel boxes. +Vesafb is a generic framebuffer driver for x86 and x86_64 boxes. -The idea is simple: Turn on graphics mode at boot time with the help -of the BIOS, and use this as framebuffer device /dev/fb0, like the m68k -(and other) ports do. - -This means we decide at boot time whenever we want to run in text or -graphics mode. Switching mode later on (in protected mode) is -impossible; BIOS calls work in real mode only. VESA BIOS Extensions -Version 2.0 are required, because we need a linear frame buffer. +VESA BIOS Extensions Version 2.0 are required, because we need a linear +frame buffer. VBE 3.0 is required if you want to use modes with a higher +(than the standard 60Hz) refresh rate. + +The VESA framebuffer driver comes in two flavors - the standard vesafb +and vesafb-tng. Vesafb-tng is available only on 32-bit x86 due to the +technology it uses (vm86). Vesafb-tng has more features than vesafb +(adjusting the refresh rate on VBE3.0-compliant boards, switching the +video mode without rebooting, selecting a mode by providing its +modedb name, and more) but might be unstable on some systems. Advantages: @@ -29,16 +31,27 @@ How to use it? ============== -Switching modes is done using the vga=... boot parameter. Read -Documentation/svga.txt for details. - -You should compile in both vgacon (for text mode) and vesafb (for -graphics mode). Which of them takes over the console depends on -whenever the specified mode is text or graphics. - -The graphic modes are NOT in the list which you get if you boot with -vga=ask and hit return. The mode you wish to use is derived from the -VESA mode number. Here are those VESA mode numbers: +If you are running your system on hardware platform where vm86 is supported +(this is 32-bit x86 only as of the time of writing this document) and you +decide to use vesafb-tng, you can either the driver into the kernel or use it +as a module. The graphic mode you want to use is in both cases specified using +the standard modedb format. + +If your system doesn't support vm86 calls yet (all 64-bit platforms), things +get a little more tricky. Since on such systems you can't do BIOS calls from +protected mode in which kernel runs, you have to decide at boot time whenever +you want to run in text or in graphics mode. Switching mode later on is +impossible. Switching modes is done using the vga=... boot parameter. Read +Documentation/svga.txt for details. Below is a more detailed description of +what to do on systems using the standard vesafb driver. + +You should compile in both vgacon (for text mode) and vesafb (for graphics mode). +Which of them takes over the console depends on whenever the specified mode is +text or graphics. + +The graphic modes are NOT in the list which you get if you boot with vga=ask +and hit return. The mode you wish to use is derived from the VESA mode number. +Here are those VESA mode numbers: | 640x480 800x600 1024x768 1280x1024 ----+------------------------------------- @@ -47,8 +60,7 @@ 64k | 0x111 0x114 0x117 0x11A 16M | 0x112 0x115 0x118 0x11B -The video mode number of the Linux kernel is the VESA mode number plus -0x200. +The video mode number of the Linux kernel is the VESA mode number plus 0x200. Linux_kernel_mode_number = VESA_mode_number + 0x200 @@ -61,10 +73,10 @@ 64k | 0x311 0x314 0x317 0x31A 16M | 0x312 0x315 0x318 0x31B -To enable one of those modes you have to specify "vga=ask" in the -lilo.conf file and rerun LILO. Then you can type in the desired -mode at the "vga=ask" prompt. For example if you like to use -1024x768x256 colors you have to say "305" at this prompt. +To enable one of those modes you have to specify "vga=ask" in the lilo.conf +file and rerun LILO. Then you can type in the desired mode at the "vga=ask" +prompt. For example if you like to use 1024x768x256 colors you have to say +"305" at this prompt. If this does not work, this might be because your BIOS does not support linear framebuffers or because it does not support this mode at all. @@ -77,6 +89,7 @@ 2. Note: Some newer versions of LILO appear to work with those hex values, if you set the 0x in front of the numbers. + X11 === @@ -86,65 +99,73 @@ The X-Server must restore the video mode correctly, else you end up with a broken console (and vesafb cannot do anything about this). +With vesafb-tng chances are that the console will be restored properly +even if the X server messed up the video mode. Refresh rates ============= -There is no way to change the vesafb video mode and/or timings after -booting linux. If you are not happy with the 60 Hz refresh rate, you -have these options: +With VBE3.0 compatible BIOSes and vesafb-tng it is possible to change +the refresh rate either at boot time (by specifying the @ part of +the mode name) or later, using the fbset utility. + +With VBE2.0 there is no way to change the mode timings after booting +Linux. If you are not happy with the 60 Hz refresh rate, you have +these options: - * configure and load the DOS-Tools for your the graphics board (if - available) and boot linux with loadlin. + * configure and load the DOS tools for your the graphics board (if + available) and boot Linux with loadlin. * use a native driver (matroxfb/atyfb) instead if vesafb. If none is available, write a new one! - * VBE 3.0 might work too. I have neither a gfx board with VBE 3.0 - support nor the specs, so I have not checked this yet. + * use a BIOS editor to change the default refresh rate (such an + editor does exist at least for ATI Radeon BIOSes). + * if you're running a non-vm86 and VBE3.0-compatible system, you can + use a kernel patch to hard-code some mode timings in the kernel and + use these while setting the graphic mode at boot time. Configuration ============= -The VESA BIOS provides protected mode interface for changing -some parameters. vesafb can use it for palette changes and -to pan the display. It is turned off by default because it -seems not to work with some BIOS versions, but there are options -to turn it on. - -You can pass options to vesafb using "video=vesafb:option" on -the kernel command line. Multiple options should be separated -by comma, like this: "video=vesafb:ypan,invers" - -Accepted options: - -invers no comment... - -ypan enable display panning using the VESA protected mode - interface. The visible screen is just a window of the +The VESA BIOS provides protected mode interface for changing some parameters. +vesafb can use it for palette changes and to pan the display. It is turned +off by default because it seems not to work with some BIOS versions, but there +are options to turn it on. + +You can pass options to vesafb using "video=vesafb:option" on the kernel +command line. Multiple options should be separated by comma, like this: +"video=vesafb:ypan,1024x768-32@85" + +Accepted options (both vesafb and vesafb-tng): + +ypan Enable display panning using the VESA protected mode + interface or vm86 calls. The visible screen is just a window of the video memory, console scrolling is done by changing the start of the window. pro: * scrolling (fullscreen) is fast, because there is no need to copy around data. - * You'll get scrollback (the Shift-PgUp thing), + * you'll get scrollback (the Shift-PgUp thing), the video memory can be used as scrollback buffer - kontra: * scrolling only parts of the screen causes some + con: * scrolling only parts of the screen causes some ugly flicker effects (boot logo flickers for example). -ywrap Same as ypan, but assumes your gfx board can wrap-around - the video memory (i.e. starts reading from top if it - reaches the end of video memory). Faster than ypan. - -redraw scroll by redrawing the affected part of the screen, this - is the safe (and slow) default. +ywrap Same as ypan, but assumes your gfx board can wrap-around the video + memory (i.e. starts reading from top if it reaches the end of video + memory). Faster than ypan. +redraw Scroll by redrawing the affected part of the screen, this is the + safe (and slow) default. -vgapal Use the standard vga registers for palette changes. +vgapal Use the standard VGA registers for palette changes. This is the default. + pmipal Use the protected mode interface for palette changes. -mtrr setup memory type range registers for the vesafb framebuffer. +mtrr Setup memory type range registers for the vesafb framebuffer. + +nomtrr Do not use memory type range registers for vesafb. vremap:n remap 'n' MiB of video RAM. If 0 or not specified, remap memory @@ -156,12 +177,96 @@ if the video BIOS of your card incorrectly determines the total amount of video RAM, use this option to override the BIOS (in MiB). -Have fun! +Options accepted only by vesafb-tng: + + The mode you want to set, in the standard modedb format. Refer to + modedb.txt for detailed description. If you specify a mode that is + not supported by your board's BIOS, vesafb will attempt to set a + similar mode. The list of supported modes can be found in + /proc/fbx/modes, where x is the framebuffer number (usually 0). + When vesafb is compiled as a module, the mode string should be + provided as a value of the parameter 'mode'. + +vbemode:x + Force the use of VBE mode x. The mode will only be set if it's + found in VBE-provided list of supported modes. + NOTE: The mode number 'x' should be specified in VESA mode number + notation, not the Linux kernel one (ie. 257 instead of 769). + HINT: If you use this option because normal parameter does + not work for you and you use a X server, you'll probably want to + set the 'nocrtc' option to ensure that the video mode is properly + restored after console <-> X switches. + +nocrtc Do not use CRTC timings while setting the graphic mode. This option + makes sence only with VBE3.0 compliant systems. Use it if you have + problems with the modes set in the standard way. Note that specifying + this option means the refresh rate will be ignored and will stay at + your BIOS' default (60 Hz). + +noedid Do not try to fetch and use EDID-provided modes. + +gtf Force the use of VESA's GTF (Generalized Timing Formula). Specifying + this will cause vesafb to skip it's internal modedb and EDID-modedb + and jump straight to the GTF part of the code (normally used only is + everything else failed). This can be useful if you want to get as much + as possible from you graphics board but your BIOS doesn't support + modes with refresh rates you require. Note that you may need to + specify the maxhf, maxvf and maxclk parameters if they are not + provided by EDID. + +Additionally, the following parameters may be provided. They all override the +EDID-provided values and BIOS defaults. Refer to you monitor's specs to get +the correct values for maxhf, maxvf and maxclk for your hardware. + +maxhf:n Maximum horizontal frequency (in kHz). +maxvf:n Maximum vertical frequency (in Hz). +maxclk:n Maximum pixel clock (in MHz). + + +Vesafb-tng Technical details +============================ + +1. The driver architecture. + +The driver's code is stored in 3 files: + /drivers/video/vesafb-tng.c + /drivers/video/vesafb-thread.c + /include/video/vesa.h + +vesafb-tng.c contains the main code. vesafb-thread.c contains code for the +vesafb service thread. A separate thread is necessary because we need to remap +memory in order to be able to use the vm86 calls. The service thread is started +regardless of whether vesafb is compiled into the kernel or compiled as a +module. This is necessary because of the active_mm stuff, better described in +the header of vesafb-thread.c. + +2. The driver initialization + + o vesafb_vbe_init + - get basic info about the graphics BIOS + - fetch data about all modes supported by VBE + - get info about the protected mode interface + - get EDID data and attempt to create an EDID modedb + + o vesafb_probe + - get service thread's PID (started earlier from fbmem.c) + - call vesafb_vbe_init + - find a matching VBE mode + - try to find the specified mode in vesa_modes modedb + - try to find the specified mode in the EDID modedb + - try to calculate timings with the GTF + - low level setup - request_mem_region, ioremap, etc. + - setup /proc/fb/modes and /proc/fb/vbe_info - Gerd +Have fun! -- +Original document for the vesafb driver by Gerd Knorr -Minor (mostly typo) changes -by Nico Schmoigl +Minor (mostly typo) changes by +Nico Schmoigl + +Extended documentation for vm86, VBE3.0 and vesafb-tng by +Micha³ Januszewski + diff -Nru a/arch/i386/boot/video.S b/arch/i386/boot/video.S --- a/arch/i386/boot/video.S 2005-03-28 23:14:56 +02:00 +++ b/arch/i386/boot/video.S 2005-03-28 23:14:56 +02:00 @@ -164,10 +164,12 @@ # parameters in the default 80x25 mode -- these are set directly, # because some very obscure BIOSes supply insane values. mode_params: +#ifdef CONFIG_FB_VESA_STD #ifdef CONFIG_VIDEO_SELECT cmpb $0, graphic_mode jnz mopar_gr #endif +#endif movb $0x03, %ah # Read cursor position xorb %bh, %bh int $0x10 @@ -200,6 +202,7 @@ ret #ifdef CONFIG_VIDEO_SELECT +#ifdef CONFIG_FB_VESA_STD # Fetching of VESA frame buffer parameters mopar_gr: leaw modelist+1024, %di @@ -278,6 +281,7 @@ movw %es, %fs:(PARAM_VESAPM_SEG) movw %di, %fs:(PARAM_VESAPM_OFF) no_pm: ret +#endif # The video mode menu mode_menu: @@ -492,10 +496,12 @@ cmpb $VIDEO_FIRST_V7>>8, %ah jz setv7 - + +#ifdef CONFIG_FB_VESA_STD cmpb $VIDEO_FIRST_VESA>>8, %ah jnc check_vesa - +#endif + orb %ah, %ah jz setmenu @@ -567,6 +573,7 @@ movw -4(%si), %ax # Fetch mode ID jmp _m_s +#ifdef CONFIG_FB_VESA_STD check_vesa: leaw modelist+1024, %di subb $VIDEO_FIRST_VESA>>8, %bh @@ -600,6 +607,7 @@ ret _setbad: jmp setbad # Ugly... +#endif # Recalculate vertical display end registers -- this fixes various # inconsistencies of extended modes on many adapters. Called when diff -Nru a/drivers/video/Kconfig b/drivers/video/Kconfig --- a/drivers/video/Kconfig 2005-03-28 23:14:56 +02:00 +++ b/drivers/video/Kconfig 2005-03-28 23:14:56 +02:00 @@ -458,7 +458,7 @@ cards. Say Y if you have one of those. config FB_VESA - bool "VESA VGA graphics support" + tristate "VESA VGA graphics support" depends on (FB = y) && (X86 || X86_64) select FB_CFB_FILLRECT select FB_CFB_COPYAREA @@ -469,6 +469,48 @@ compliant graphic cards. The older VESA 1.2 cards are not supported. You will get a boot time penguin logo at no additional cost. Please read . If unsure, say Y. + +choice + prompt "VESA driver type" + depends on FB_VESA + default FB_VESA_STD if X86_64 + default FB_VESA_TNG if X86 + +config FB_VESA_STD + bool "vesafb" + help + This is the frame buffer device driver for generic VESA 2.0 + compliant graphic cards. The older VESA 1.2 cards are not supported. + You will get a boot time penguin logo at no additional cost. Please + read . Choose this driver if you + are experiencing problems with vesafb-tng or if you own a 64-bit system. + + Note that this driver cannot be compiled as a module. + +config FB_VESA_TNG + bool "vesafb-tng" + depends on !X86_64 + select FB_MODE_HELPERS + help + This is the frame buffer device driver for generic VESA 2.0 + compliant graphic cards. It is capable of taking advantage of + VBE 3.0 features. With this driver you will be able to adjust + the refresh rate (VBE 3.0 compliant boards only) and change + the graphic mode on-the-fly. + + You will also get a boot time penguin logo at no additional cost. Please + read . + +endchoice + +config FB_VESA_DEFAULT_MODE + string "VESA default mode" + depends on FB_VESA_TNG + default "640x480@60" + help + This option is used to determine the default mode vesafb is + supposed to switch to in case no mode is provided as a kernel + command line parameter. config VIDEO_SELECT bool diff -Nru a/drivers/video/Makefile b/drivers/video/Makefile --- a/drivers/video/Makefile 2005-03-28 23:14:56 +02:00 +++ b/drivers/video/Makefile 2005-03-28 23:14:56 +02:00 @@ -90,7 +90,22 @@ obj-$(CONFIG_FB_TX3912) += tx3912fb.o # Platform or fallback drivers go here -obj-$(CONFIG_FB_VESA) += vesafb.o +ifeq ($(CONFIG_FB_VESA),m) + ifeq ($(CONFIG_FB_VESA_STD),y) + obj-y += vesafb.o + else + obj-m += vesafb-tng.o + obj-y += vesafb-thread.o + endif +else + ifeq ($(CONFIG_FB_VESA),y) + ifeq ($(CONFIG_FB_VESA_STD),y) + obj-y += vesafb.o + else + obj-y += vesafb-tng.o vesafb-thread.o + endif + endif +endif obj-$(CONFIG_FB_VGA16) += vga16fb.o vgastate.o obj-$(CONFIG_FB_OF) += offb.o diff -Nru a/drivers/video/fbmem.c b/drivers/video/fbmem.c --- a/drivers/video/fbmem.c 2005-03-28 23:14:56 +02:00 +++ b/drivers/video/fbmem.c 2005-03-28 23:14:56 +02:00 @@ -52,6 +52,8 @@ * Frame buffer device initialization and setup routines */ +extern int vesafb_init_thread(void); + #define FBPIXMAPSIZE (1024 * 8) static struct notifier_block *fb_notifier_list; @@ -1203,6 +1205,10 @@ printk(KERN_WARNING "Unable to create fb class; errno = %ld\n", PTR_ERR(fb_class)); fb_class = NULL; } + +#if defined(CONFIG_FB_VESA_TNG) || defined(CONFIG_FB_VESA_TNG_MODULE) + vesafb_init_thread(); +#endif return 0; } diff -Nru a/drivers/video/fbmon.c b/drivers/video/fbmon.c --- a/drivers/video/fbmon.c 2005-03-28 23:14:56 +02:00 +++ b/drivers/video/fbmon.c 2005-03-28 23:14:56 +02:00 @@ -518,7 +518,7 @@ * This function builds a mode database using the contents of the EDID * data */ -static struct fb_videomode *fb_create_modedb(unsigned char *edid, int *dbsize) +struct fb_videomode *fb_create_modedb(unsigned char *edid, int *dbsize) { struct fb_videomode *mode, *m; unsigned char *block; @@ -593,7 +593,7 @@ kfree(modedb); } -static int fb_get_monitor_limits(unsigned char *edid, struct fb_monspecs *specs) +int fb_get_monitor_limits(unsigned char *edid, struct fb_monspecs *specs) { int i, retval = 1; unsigned char *block; @@ -1197,9 +1197,17 @@ { return NULL; } +struct fb_videomode *fb_create_modedb(unsigned char *edid, int *dbsize) +{ + return NULL; +} void fb_destroy_modedb(struct fb_videomode *modedb) { } +int fb_get_monitor_limits(unsigned char *edid, struct fb_monspecs *specs) +{ + return 1; +} int fb_get_mode(int flags, u32 val, struct fb_var_screeninfo *var, struct fb_info *info) { @@ -1275,3 +1283,5 @@ EXPORT_SYMBOL(fb_get_mode); EXPORT_SYMBOL(fb_validate_mode); EXPORT_SYMBOL(fb_destroy_modedb); +EXPORT_SYMBOL(fb_create_modedb); +EXPORT_SYMBOL(fb_get_monitor_limits); diff -Nru a/drivers/video/vesafb-thread.c b/drivers/video/vesafb-thread.c --- /dev/null Wed Dec 31 16:00:00 196900 +++ b/drivers/video/vesafb-thread.c 2005-03-28 23:14:56 +02:00 @@ -0,0 +1,569 @@ +/* + * Framebuffer driver for VBE 2.0+ compliant graphic boards - kernel thread + * and vm86 routines. + * + * This code has to be compiled into the kernel even if vesafb is configured + * as a module. If vesafb_thread were to be started while the module is being + * initialized, it would share its active_mm with modprobe. This mm would be + * lost after modprobe finished its work, and we can't allow it, because we + * need it for as long as the vesafb thread is active. + * + * (c) 2004 Micha³ Januszewski + * + */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include