From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Kendall Bennett <KendallB@scitechsoft.com>, linux-kernel@vger.kernel.org
Cc: linux-fbdev-devel@lists.sourceforge.net,
penguinppc-team@lists.penguinppc.org
Subject: Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT?
Date: Fri, 15 Oct 2004 08:27:38 +0800 [thread overview]
Message-ID: <200410150827.38943.adaplas@hotpop.com> (raw)
In-Reply-To: <416E6ADC.3007.294DF20D@localhost>
On Friday 15 October 2004 03:02, Kendall Bennett wrote:
> So what we would like to find out is how much interest there might be in
> both an updated VESA framebuffer console driver as well as the code for
> the Video card BOOT process being contributed to the maintstream kernel.
> If there is interest, we would start out by first contributing the core
> emulator and Video BOOT code, and then work on building a better VESA
> framebuffer console driver.
>
> So what do you guys think?
>
I'm for it, if you can get the code in the kernel. If not, what are the
arguments against doing this in userspace?
If you remember about 2 years ago, there was a thread which you started
about vesafbd. From that, I've worked on vm86d which is a generic approach
to running BIOS code in user space. I stopped development on this though,
but it should be easy to revive. There is also vesafb-tng. I think it runs
BIOS code in kernel space.
The video BOOT code is also nice, especially for non-primary graphics cards.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
"Kendall Bennett" <KendallB@scitechsoft.com>,
linux-kernel@vger.kernel.org
Cc: linux-fbdev-devel@lists.sourceforge.net,
penguinppc-team@lists.penguinppc.org
Subject: Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT?
Date: Fri, 15 Oct 2004 08:27:38 +0800 [thread overview]
Message-ID: <200410150827.38943.adaplas@hotpop.com> (raw)
In-Reply-To: <416E6ADC.3007.294DF20D@localhost>
On Friday 15 October 2004 03:02, Kendall Bennett wrote:
> So what we would like to find out is how much interest there might be in
> both an updated VESA framebuffer console driver as well as the code for
> the Video card BOOT process being contributed to the maintstream kernel.
> If there is interest, we would start out by first contributing the core
> emulator and Video BOOT code, and then work on building a better VESA
> framebuffer console driver.
>
> So what do you guys think?
>
I'm for it, if you can get the code in the kernel. If not, what are the
arguments against doing this in userspace?
If you remember about 2 years ago, there was a thread which you started
about vesafbd. From that, I've worked on vm86d which is a generic approach
to running BIOS code in user space. I stopped development on this though,
but it should be easy to revive. There is also vesafb-tng. I think it runs
BIOS code in kernel space.
The video BOOT code is also nice, especially for non-primary graphics cards.
Tony
next prev parent reply other threads:[~2004-10-15 0:27 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 19:02 Generic VESA framebuffer driver and Video card BOOT? Kendall Bennett
2004-10-14 19:59 ` Zachary Smith
2004-10-15 23:36 ` Ian Romanick
2004-10-14 20:48 ` Zachary Smith
2004-10-15 18:05 ` Kendall Bennett
2004-10-15 18:55 ` Zachary Smith
2004-10-15 19:18 ` Geert Uytterhoeven
2004-10-15 22:22 ` Kendall Bennett
2004-10-15 0:27 ` Antonino A. Daplas [this message]
2004-10-15 0:27 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-15 23:20 ` Jon Smirl
2004-10-15 23:51 ` Kendall Bennett
2004-10-15 23:58 ` Jon Smirl
2004-10-19 21:15 ` Pavel Machek
2004-10-16 1:50 ` Antonino A. Daplas
2004-10-16 1:50 ` Antonino A. Daplas
2004-10-16 2:03 ` Jon Smirl
2004-10-18 19:34 ` Kendall Bennett
2004-10-18 19:34 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-18 20:34 ` Richard Smith
2004-10-18 20:34 ` [Linux-fbdev-devel] " Richard Smith
2004-10-18 20:47 ` Kendall Bennett
2004-10-18 21:04 ` Richard Smith
2004-10-18 21:16 ` Jon Smirl
2004-10-18 22:34 ` Richard Smith
2004-10-18 22:34 ` [Linux-fbdev-devel] " Richard Smith
2004-10-18 23:28 ` Jon Smirl
2004-10-19 0:18 ` Richard Smith
2004-10-19 0:18 ` [Linux-fbdev-devel] " Richard Smith
2004-10-19 0:55 ` Kendall Bennett
2004-10-19 1:39 ` Richard Smith
2004-10-19 1:39 ` [Linux-fbdev-devel] " Richard Smith
2004-10-19 17:54 ` Kendall Bennett
2004-10-19 17:54 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:48 ` Pavel Machek
2004-10-20 17:01 ` Kendall Bennett
2004-10-20 17:01 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 19:08 ` Pavel Machek
2004-10-21 19:36 ` Kendall Bennett
2004-10-21 19:36 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:42 ` Pavel Machek
2004-10-15 12:05 ` Gerd Knorr
2004-10-15 12:38 ` Geert Uytterhoeven
2004-10-15 12:45 ` Alan Cox
2004-10-19 21:54 ` Pavel Machek
2004-10-15 13:13 ` Gerd Knorr
2004-10-17 12:07 ` Martin Waitz
2004-10-18 8:36 ` Gerd Knorr
2004-10-18 8:36 ` [Linux-fbdev-devel] " Gerd Knorr
2004-10-18 11:39 ` Martin Waitz
2004-10-18 12:10 ` Gerd Knorr
2004-10-18 12:10 ` [Linux-fbdev-devel] " Gerd Knorr
2004-10-18 20:21 ` Helge Hafting
2004-10-18 20:42 ` Oliver Neukum
2004-10-19 16:57 ` Martin Waitz
2004-10-15 18:29 ` Venkatesh Pallipadi
2004-10-16 9:01 ` Nigel Cunningham
2004-10-16 9:01 ` [Linux-fbdev-devel] " Nigel Cunningham
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 13:48 ` Helge Hafting
2004-10-15 13:48 ` Helge Hafting
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 21:44 ` Helge Hafting
2004-10-15 22:12 ` Kendall Bennett
2004-10-16 0:41 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-16 0:41 ` Antonino A. Daplas
2004-10-26 11:14 ` Paulo Marques
2004-10-26 11:14 ` Paulo Marques
2004-10-27 1:58 ` Kendall Bennett
2004-10-27 11:11 ` Paulo Marques
2004-10-27 19:52 ` Kendall Bennett
2004-10-27 19:52 ` Kendall Bennett
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-16 17:44 ` Jon Smirl
2004-10-16 17:44 ` Jon Smirl
2004-10-18 19:34 ` Kendall Bennett
2004-10-18 19:34 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:00 ` Pavel Machek
2004-10-19 21:11 ` Pavel Machek
2004-10-20 17:01 ` Kendall Bennett
2004-10-20 17:01 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 17:31 ` Pavel Machek
2004-10-20 18:44 ` Kendall Bennett
2004-10-20 18:44 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 19:10 ` Pavel Machek
2004-10-21 19:36 ` Kendall Bennett
2004-10-21 19:36 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-21 20:47 ` Richard Smith
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=200410150827.38943.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=KendallB@scitechsoft.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=penguinppc-team@lists.penguinppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.