From: "Antonino A. Daplas" <adaplas@gmail.com>
To: spock@gentoo.org, linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] fbdev: uvesafb
Date: Thu, 12 Jul 2007 16:12:01 +0800 [thread overview]
Message-ID: <1184227922.4504.22.camel@daplas> (raw)
In-Reply-To: <20070623104920.GA12623@spock.one.pl>
On Sat, 2007-06-23 at 12:49 +0200, Michal Januszewski wrote:
My apologies for the delayed response. I had problems with my ISP.
> uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
> version of vesafb and a direct successor of vesafb-tng [1].
>
> uvesafb uses a userspace helper application (v86d, [2]) to run the x86
> Video BIOS code. This makes it possible to include in uvesafb all the
> standard features (refresh rate control, video mode changes etc) that
> are missing from vesafb without resorting to ugly hacks such as the ones
> used in [1]. The current implementation of v86d can use either LRMI or
> x86emu to run the BIOS code and supports both x86 and x86_64.
>
> [1] http://dev.gentoo.org/~spock/projects/vesafb-tng/
> [2] http://dev.gentoo.org/~spock/projects/uvesafb/
>
This is cool, I had a similar project before (which did work) but
abandoned it. In fact, it need not be restricted to vbe, as long as the
userspace daemon can interpret VESA.
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-07-12 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 10:49 [PATCH 0/4] fbdev: uvesafb Michal Januszewski
2007-06-23 12:04 ` Arnd Bergmann
2007-06-23 12:30 ` Michal Januszewski
2007-06-26 10:42 ` Jonathan McDowell
2007-06-30 16:39 ` Michal Januszewski
2007-07-12 8:12 ` Antonino A. Daplas [this message]
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=1184227922.4504.22.camel@daplas \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@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;
as well as URLs for NNTP newsgroup(s).