From: "H. Peter Anvin" <hpa@zytor.com>
To: Jonathan Campbell <jon@nerdgrounds.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org
Subject: Re: Vramfs: filesystem driver to utilize extra RAM on VGA devices
Date: Mon, 26 Jan 2009 15:36:57 -0800 [thread overview]
Message-ID: <497E4919.60907@zytor.com> (raw)
In-Reply-To: <497E4531.20800@nerdgrounds.com>
Jonathan Campbell wrote:
>
> So far I've tested it against 2.6.25.17 and 2.6.28 on both x86 and
> x86_64 with reads, writes, directory creation, symlink creation, and
> mmap() and it seems to work fine.
> Just give it a range of memory on the bus, or the
> domain:bus:device:function numbers of a VGA PCI device, and it will
> mount the VGA video RAM and allow files to exist there.
> As a special hack: you can also specify the size of the active
> framebuffer console so that fbcon doesn't collide with this driver
> (unless you want to see what your files look like splattered across your
> screen, ha). The active VRAM area becomes a "sentinel" file named
> "framebuffer".
>
> What do you guys think?
>
How is this different from the MTD driver we already have?
-hpa
next prev parent reply other threads:[~2009-01-26 23:37 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 [this message]
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
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=497E4919.60907@zytor.com \
--to=hpa@zytor.com \
--cc=devel@driverdev.osuosl.org \
--cc=jon@nerdgrounds.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