From: "Ai Chengshi" <rosemaryai@vip.sina.com>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: About framebuffer driver
Date: Tue, 3 Feb 2004 09:12:01 +0800 [thread overview]
Message-ID: <002801c3e9f2$c63fe720$3d01a8c0@tcentel.com> (raw)
In-Reply-To: Pine.LNX.4.44.0402021759470.27538-100000@phoenix.infradead.org
If I want to transfer data in frame buffer to LCD GRAM, where should I add this function to?
Sincerely,
Ai Chengshi
----- Original Message -----
From: "James Simmons" <jsimmons@infradead.org>
To: <rosemaryai@vip.sina.com>
Cc: <linux-fbdev-devel@lists.sourceforge.net>
Sent: Tuesday, February 03, 2004 2:00 AM
Subject: Re: [Linux-fbdev-devel] About framebuffer driver
>
> > The kernel I am using is 2.4. When I copy test.bin to /dev/fbdir/0, which function does the Linux call?
>
> fb_write.
>
>
>
next prev parent reply other threads:[~2004-02-03 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 1:38 About framebuffer driver rosemaryai
2004-02-02 18:00 ` James Simmons
2004-02-03 1:02 ` Ai Chengshi
2004-02-03 1:12 ` Ai Chengshi [this message]
2004-02-04 23:52 ` Antonino A. Daplas
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='002801c3e9f2$c63fe720$3d01a8c0@tcentel.com' \
--to=rosemaryai@vip.sina.com \
--cc=jsimmons@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).