From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: 8 words bursts for fbdev driver
Date: Mon, 28 May 2007 23:40:08 +0800 [thread overview]
Message-ID: <1180366808.4526.4.camel@daplas> (raw)
In-Reply-To: <1180365959.465af4876a6a8@imp.free.fr>
On Mon, 2007-05-28 at 17:25 +0200, xcsnake@free.fr wrote:
> Hello,
>
> I have posted this message on the linux-kernel mailing list, but I think it
> could be more appropriate here.
> I'm working on a FPGA vga controller, with an arm cpu (at91rm9200). My FPGA is
> plugged on a 16 bits data bus. I'm trying to develop the framebuffer driver,
> from the epson s1d13xxxfb driver to use my controller. I have a first driver
> which works well. To accelerate my controller, I would like to read and write in
> my video memory (controlled by the FPGA) by 8 words bursts. Is it possible to
> tell the kernel that the memory must be accessed only by 8 words bursts ??
> My driver is available on http://xcsnake.free.fr/driver
You can write your own fillrect, imageblit and copyarea routine. The
same with fb_read and fb_write. For userland that mmap's the
framebuffer, I don't think there's a way to tell them how to access the
framebuffer.
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-05-28 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 15:25 8 words bursts for fbdev driver xcsnake
2007-05-28 15:40 ` Antonino A. Daplas [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-28 11:11 xcsnake
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=1180366808.4526.4.camel@daplas \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.