From: "H. Peter Anvin" <hpa@zytor.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Jonathan Campbell <jon@nerdgrounds.com>,
"Peter W. Morreale" <pmorreale@novell.com>,
devel@driverdev.osuosl.org,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Vramfs: filesystem driver to utilize extra RAM on VGA devices
Date: Thu, 29 Jan 2009 21:25:34 -0800 [thread overview]
Message-ID: <49828F4E.40208@zytor.com> (raw)
In-Reply-To: <20090130052007.GM5038@1wt.eu>
Willy Tarreau wrote:
>
> Also, MTD allows you to map *part* of the VRAM. On my laptop, I only
> map 56 MB out of the 64 MB of VRAM, which still allows me to use the
> VGA normally. And BTW, I map this VRAM as a fast swap memory.
>
> In fact, I see little use to the VRAMFS for the average user. Still
> it might have been a nice coding exercice for Jonathan.
>
Also, the idea of using the DMA engine on the video card rather than
just doing PIO references is an excellent one.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-01-30 5:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 23:20 Vramfs: filesystem driver to utilize extra RAM on VGA devices Jonathan Campbell
2009-01-26 23:36 ` H. Peter Anvin
2009-01-26 23:50 ` Jonathan Campbell
2009-01-29 17:04 ` Peter W. Morreale
2009-01-29 17:30 ` Jonathan Campbell
2009-01-29 17:38 ` H. Peter Anvin
2009-01-30 3:19 ` Jonathan Campbell
2009-01-30 4:46 ` H. Peter Anvin
2009-01-30 5:20 ` Willy Tarreau
2009-01-30 5:25 ` H. Peter Anvin [this message]
2009-01-27 2:59 ` Mark Knecht
2009-01-27 4:44 ` Eric Anholt
2009-01-27 17:37 ` Mark Knecht
2009-01-27 21:23 ` Eric Anholt
2009-01-28 6:36 ` Jonathan Campbell
2009-01-28 7:05 ` Dave Airlie
2009-01-28 9:03 ` Jonathan Campbell
2009-01-28 9:42 ` Dave Airlie
2009-01-27 5:07 ` Jonathan Campbell
2009-01-27 18:18 ` Mark Knecht
[not found] ` <497F60A3.6020608@nerdgrounds.com>
2009-01-27 20:49 ` Mark Knecht
2009-01-27 21:15 ` Jonathan Campbell
2009-01-28 6:59 ` Trent Piepho
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=49828F4E.40208@zytor.com \
--to=hpa@zytor.com \
--cc=devel@driverdev.osuosl.org \
--cc=jon@nerdgrounds.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmorreale@novell.com \
--cc=w@1wt.eu \
/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.