From: Kromer <krom@gazeta.pl>
To: linux-mm@kvack.org
Subject: framebuffer mmap
Date: Thu, 09 Oct 2003 10:58:22 +0200 [thread overview]
Message-ID: <3F85232E.6090604@gazeta.pl> (raw)
hello mm-everybody
i'm just writing my own framebuffer driver for device acessed only via
parallel port (there is no way to direct read/write it's memory)
i just want to use memory allocated in kernel module, and acess it
application with mmmap (and of course flush this memory to device
peridicaly)
q1: where is documentation of writing own mmap functions
q2: what fields need to be set in mmap function implementation
q3: what kind of memory allocation i should use inside driver
(kmalloc, vmalloc, with GFP_KERNEL or FGP_USER?)
q4: how to remap (or not?) in mmap function
q5: is there any simply way to build acess for non-direct memory ?
i mean for each byte read/write to this
memory need to be called my own function
please answer to my priv (mailto:krom@gazeta.pl) too
thx
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2003-10-09 8:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F85232E.6090604@gazeta.pl \
--to=krom@gazeta.pl \
--cc=linux-mm@kvack.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