From: Michal Januszewski <spock@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: [gentoo-kernel] [announce] vesafb-tng-1.0-rc2
Date: Thu, 29 Jun 2006 19:58:13 +0200 [thread overview]
Message-ID: <20060629175813.63EEA18165CC@ipp23-131.piekary.net> (raw)
-git-20060629 released
Message-ID: <20060629175813.GA8544@spock.one.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Disposition: inline
X-PGP-Key: http://dev.gentoo.org/~spock/spock.gpg
User-Agent: Mutt/1.5.11
This is an automated message announcing the release of a new version
of the vesafb-tng kernel patch.
Excerpt from the ChangeLog
--------------------------
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).
Link to the patch
-----------------
http://dev.gentoo.org/~spock/projects/vesafb-tng/archive/vesafb-tng-1.0-rc2-git-20060629.patch
The patch was generated against Linus' linux-2.6 git tree.
Release notes
-------------
None this time.
About vesafb-tng
----------------
vesafb-tng is an extended version of the vesafb Linux framebuffer driver.
For more information, visit the project homepage:
http://dev.gentoo.org/~spock/projects/vesafb-tng/
Please read the FAQ and the Troubleshooting Guide before reporting any
bugs and problems.
--
gentoo-kernel@gentoo.org mailing list
reply other threads:[~2006-06-29 17:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060629175813.63EEA18165CC@ipp23-131.piekary.net \
--to=spock@gentoo.org \
--cc=gentoo-kernel@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox