From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Thomas Koeller <thomas@koeller.dyndns.org>
Cc: adaplas@pol.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] non-linear frame buffer read/write access
Date: Sat, 07 Jan 2006 05:25:43 +0800 [thread overview]
Message-ID: <43BEE057.6000603@gmail.com> (raw)
In-Reply-To: <200601032339.24927.thomas@koeller.dyndns.org>
Thomas Koeller wrote:
> While the code in fbmem.c allows for hooking read/write access
> to non-linear frame buffers by means of fb_read and fb_write
> in struct fb_ops, I could not find a way tho access the actual
> frame buffer memory from within these routines. I therefore
> had to patch fbmem.c, to be able to retrieve a pointer to
> struct fb_info from the 'file' argument to these functions.
>
> The second hunk of the patch is not strictly required, I only
> did that for symmetry reasons (and the code is somewhat
> shorter).
>
> Patch is against 2.6.14
>
> Signed-off-by: Thomas Koeller <thomas@koeller.dyndns.org>
Okay.
Tony
prev parent reply other threads:[~2006-01-08 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 22:39 [PATCH] non-linear frame buffer read/write access Thomas Koeller
2006-01-06 21:25 ` Antonino A. Daplas [this message]
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=43BEE057.6000603@gmail.com \
--to=adaplas@gmail.com \
--cc=adaplas@pol.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@koeller.dyndns.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.