From: "Kendall Bennett" <KendallB@scitechsoft.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Help with patch for vesafbd support again?
Date: Wed, 19 Mar 2003 11:25:45 -0800 [thread overview]
Message-ID: <3E7853B9.13125.8F8AA5C@localhost> (raw)
In-Reply-To: <1409.4.64.238.61.1048042813.squirrel@www.osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
> > Finally, before I embark on this project, will this patch will be accepted
> > into the kernel source code tree? I would hate to spend my time on it only
> > to find out that the kernel developers don't like it and won't accept it.
>
> Can (will) you say *why* you want this? I can't find that info here.
Why? I thought that would be clearly obvious. Right now with the VESA
framebuffer device driver you cannot change the mode on the graphics card
once the system has started. You are also restricted to only working with
VESA 2.0 cards that have functional 32-bit protected mode functions if
you wish to support panning and proper color map progamming, which is not
always possible (believe me, I know of many that will not work unless you
play magic with the selectors passed to the functions; something Linux
cannot do).
With the vesafbd driver it is possible to use 'fbset' to change the
active console display mode at any time after the system has booted, as
well as use the fallback BIOS functions to program the palette and pan
the display. Not as fast as the VBE 2.0 functions, but if the VBE 2.0
functions are broken this is a good compromise.
On top of that I already mentioned the fact that it would allow
framebuffer console drivers to be developed inside the daemon that could
be implemented using XFree86 4.0 modules if desired (ie: sharing source
code with XFree86 rather than having completely separate framebuffer
console modules developed for all the same graphics cards).
> and can you post the patch file (source code) that you have
> somewhere, like a web page (not email if it's large)?
The patch is not very large. However I have put the original release
files up on my private web page for people to download and examine:
http://www.scitechsoft.com/~kendallb/vesafbd/vesafb-20000122.patch
http://www.scitechsoft.com/~kendallb/vesafbd/vesafbd-0.1.tar.gz
Regards,
---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com
~ SciTech SNAP - The future of device driver technology! ~
next prev parent reply other threads:[~2003-03-19 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 8:25 2.4 delayed acks don't work, fixed Andrea Arcangeli
2003-03-18 18:34 ` kuznet
2003-03-18 19:34 ` Andrea Arcangeli
2003-03-18 20:13 ` kuznet
2003-03-18 22:19 ` Andrea Arcangeli
2003-03-18 22:35 ` kuznet
[not found] ` <20030319002409.GI30541@dualathlon.random>
2003-03-19 0:37 ` David S. Miller
2003-03-19 0:58 ` Andrea Arcangeli
2003-03-19 1:33 ` Help with patch for vesafbd support again? Kendall Bennett
2003-03-19 3:00 ` Randy.Dunlap
2003-03-19 19:25 ` Kendall Bennett [this message]
2003-03-19 1:55 ` 2.4 delayed acks don't work, fixed Andi Kleen
2003-03-19 2:02 ` David S. Miller
2003-03-19 19:48 ` Andrea Arcangeli
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=3E7853B9.13125.8F8AA5C@localhost \
--to=kendallb@scitechsoft.com \
--cc=linux-kernel@vger.kernel.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