vesafb-tng::ChangeLog
24 Dec 2006 * <spock@gentoo.org> * vesafb-tng-1.0-rc2-2.6.20-rc2
- Fix a potential buffer overflow in the proc handler.
23 Dec 2006 * <spock@gentoo.org> * vesafb-tng-1.0-rc2-2.6.20-rc1
- Rediffed to apply cleanly against 2.6.20-rc1.
22 Oct 2006 * <spock@gentoo.org> * vesafb-tng-1.0-rc2-2.6.19-rc2
- Rediffed to apply cleanly against 2.6.19-rc2.
29 Jun 2006 * <spock@gentoo.org> * vesafb-tng-1.0-rc2-git-20060629
- Always compile the CFB* helper modules directly into the kernel.
This allows us to avoid the "undefined reference to 'cfb_fillrect'" bug
when the standard vesafb driver is selected as a module.
- Add support for fb_open and fb_release. With the new console binding
mechanism, it is now possible to unbind fbcon and go back to the text
mode.
- Follow upstream (vesafb) changes wrt palette setting.
- Fix a stupid bug in the memory mapping code (fixes some strange
segfaults).
22 Mar 2006 * <spock@gentoo.org> * vesafb-tng-1.0-rc1-r3-2.6.16
- Rediffed to apply cleanly to a 2.6.16 vanilla kernel tree.
13 Nov 2005 * <spock@gentoo.org> * vesafb-tng-1.0-rc1-r3-2.6.15-rc1
- Merged upstream changes from vesafb;
- disable MTRR by default,
- fix vesafb_setcolreg() internals.
- Fixed a VM_RESERVED-related oops that some SMP users were
experiencing.
- Upgraded the driver to use the platform_driver framework.
29 Oct 2005 * <spock@gentoo.org> * vesafb-tng-1.0-rc1-r2-2.6.14
- Merged blanking code fixes from vesafb.
17 Oct 2005 * <spock@gentoo.org> * vesafb-tng-1.0-rc1-r1-2.6.14-rc4
- Updated the initial mode setting code so that it uses the
fb_find_nearest_mode() function.
- Fixed the function so that it does what it is supposed to do.
02 Oct 2005 * <spock@gentoo.org> * vesafb-tng-1.0-rc1-2.6.14-rc3
- Fixed SMP and HIGHMEM64G issues.
- Changed the mode setting and timings checking code, so that
modes set from the kernel command line and using fbset are
consistent.
- Added a workaround for sis6326 (which tries to read data from
the 0x07000-0x07fff area).
- Fixed numerous problems in the backend code.
- Made the backend and frontend separate modules.
- Cleaned the code up so that it adheres to the kernel CodingStyle.
- Updated the documentation.
- Added support for blanking the screen.
- Added support for the fb_setcmap() function.
- Reorganized and partially rewritten palette setting code.
09 Aug 2005 * <spock@gentoo.org> * vesafb-tng-0.9-rc7-r1-2.6.13-rc6
- Imported MTRR updates from the vesafb driver.
28 Jun 2005 * <spock@gentoo.org> * vesafb-tng-0.9-rc7-r1-2.6.13-rc1
- Fixed compilation problems with GCC < 4.0.
27 Jun 2005 * <spock@gentoo.org> * vesafb-tng-0.9-rc7-2.6.12-git-20050627
- Fixed compilation problems with GCC 4.0 (thanks go to Christian Heim
<christian.th.heim(at)gmx.de> for reporting the problem and providing
a fix).
- Fixed a potential kernel oops which could occur if the user was
attempting to use a video mode that requires more memory than vesafb-tng
had remapped at boot.
- Attempted to decrease memory usage. So far vesafb-tng has been
using 0x20000 bytes for the vm86 environment. This was a "safe"
value and has now been lowered to 0x4000. If this causes any problems,
please report back to me.
08 Mar 2005 * <spock@gentoo.org> * vesafb-tng-0.9-rc6-r2-2.6.12-rc1
- Fixed compilation problems for people not using CONFIG_FB_MODE_HELPERS.
Thanks to Imago for spotting it and providing a fix.
21 Mar 2005 * <spock@gentoo.org> * vesafb-tng-0.9-rc6-r1-2.6.12-rc1
- Updated the patch so that it can be applied cleanly against 2.6.12-rc1.
- Added an additional check for page-alignment in the MTRR code.
This might fix some problems described in the Gentoo bug #77674.
15 Jan 2005 * <spock@gentoo.org> * vesafb-tng-0.9-rc6-2.6.11-rc1
- Made video option parsing more fool-proof, this should help with
all problems about 'unspecified witdth' caused by using options
that are no longer available (like vram:)
- Fixed delayed console switches for people using the 'redraw' option.
- Fixed a MTRR problem. It has been fixed upstream for quite some time,
but somehow I forgot to change one line of code when I was importing
the fix from vesafb in some previous release, I'm sorry :)
21 Nov 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc5-2.6.10-rc2
- Added a fix for bug #69268 which made it impossible to use vesafb-tng
as a module.
01 Nov 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc5-2.6.10-rc1-bk11
- Fixed a bug in the mode-matching code that could cause vesafb-tng
not to work on some systems.
28 Oct 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-r3-2.6.10-rc1
- Updated to work 2.6.10-rc1.
- Merged some code from vesafb. 'vram' is no more, it has been
replaced with 'vremap' and 'vtotal'.
21 Aug 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-r3-2.6.9
- Updated vesafb-tng to automatically select FB_MODE_HELPERS
in the kernel config.
01 Oct 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-r3-2.6.9-rc3
- Updated vesafb-tng to patch cleanly against 2.6.9-rc3.
15 Sep 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-r3-2.6.9-rc2
- Updated the vesafb-tng patch to work with 2.6.9-rc2.
10 Sep 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-r3-2.6.9-rc1
- Changed the VBE mode matching and mode setting logic.
- Cleaned up the code.
- Removed the code for copying OEM data from RAM, as it could
cause more problems than it was supposed to solve.
27 Aug 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-r2-2.6.8.1
- Check AX (and not EAX) for the return code. Some BIOSes modify
the higher 16 bits of the register.
- Made selecting VESA text modes with vga= possible.
24 Aug 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-r1-2.6.8.1
- Fixed Makefile to allow not to build any VESA driver ;>
- Fixed Kconfig to not allow to choose vesafb-tng on x86_64.
- Added support for 8 bit DAC palette setting (changes forward-
-ported from vesafb).
- Fixed a bug which caused maxclk to be set to 0 in some cases.
- Fixed a bug which caused vesafb-tng to tell the BIOS 'to not
clear video memory' instead of 'to use the linear framebuffer'.
- Cleaned the code a *little* bit.
16 Aug 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc4-2.6.8.1
- Changed the way vesafb configuration is handled. Vesafb-tng no
longer overrides the standard vesafb driver, it provides an
alternative to it instead. If you've been a vesafb-tng and
haven't experienced any problems with it, just choose 'vesafb-tng'
as the VESA driver and you shouldn't notice any changes.
The reasons for the change introduced by this version:
- makes vesafb-tng code cleaner
- there are some users for whom vesafb-tng does not work
(I'm working on fixing this)
14 Aug 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc3-r4-2.6.8.rc1
- Fixed a SMP bug. If you were getting:
kernel BUG at arch/i386/kernel/smp.c:359
with the previous vesafb-tng versions, it's definitely time to
upgrade. If you weren't, this new version won't change anything
for you.
24 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc3-r3-2.6.8-rc1
- Fixed a typo that caused maxhf to be overridden by maxvf and
maxvf never set properly.
21 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc3-r2-2.6.8-rc1
- Included a few additional fixes for the ypanning initialization
(HWACCEL flag is now set after the scrolling method is determined
for good).
- Changed vram logic. It can now be used to override anything, it's
possible to specify an amount of VRAM higher than what the BIOS
reports.
- Added some additional error messages, removed unnecessary info
mesgs (the monitor vendor sign is a good example of such a bloat).
- Changed monitor limits logic. If no monitor limits are specified,
the user can set any mode (not just 60 Hz). If monitor limits are
specified, but there is no maxclock, it's automatically set to
300 MHz. If VBE < 3.0, EDID and monitor limits are ignored.
19 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc3-r1-2.6.8-rc1
- Fixed ywrap problems (it turned out it's a bad idea to do ypanning
via vm86).
16 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc3-2.6.8-rc1
- Made it patch cleanly against vanilla-2.6.8-rc1.
- Removed support for doublelined and interlaced modes (from the fb's
point of view at least), this is necessary because of how the new
fbcon code works (we don't want to end up running at 1024x384 just
because fbcon thought it can set a 1024x768 interlaced mode).
- The framebuffer size is now automatically limited to 16 MiB, just as
in the standard vesafb. This should make people's life easier, no
more need for the vram:16 option.
28 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc2-2.6.7
20 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc1-r1-2.6.7
20 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc1-2.6.7
13 Jul 2004 * <spock@gentoo.org> * vesafb-tng-0.9-rc1-2.6.7-rc2
