From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: porting fb driver to 2, 6(fb_get_fix, fb_get_var)
Date: Mon, 12 Jun 2006 20:44:51 +0800 [thread overview]
Message-ID: <448D61C3.2070703@gmail.com> (raw)
In-Reply-To: <20060612122624.70277.qmail@web37915.mail.mud.yahoo.com>
syed khader wrote:
> Hi,
> I am trying to port one of our LCD display frame
> buffer driver to 2.6 kernel.
> The old 2.4 kernel had these functions defined in
> fb_ops
> fb_open:
> fb_release:
These 2 are still in 2.6, but they're optional.
> fb_get_fix:
> fb_get_var:
Gone.
> fb_set_var:
The above is split into:
fb_check_var() - see if the requested var is compatible
and if not, round up to the next
legal value
fb_set_par() - set the hardware based on the current
var
> fb_get_cmap:
gone
> fb_set_cmap:
replaced by fb_setcolreg()
> fb_ioctl:
optional.
Additional required ops for 2.6.
fb_imageblit - expand monochrome to color and/or
expand 8-bit pseudocolor to color
Generic version for packed-pixel: cfb_imageblit
fb_fillrect - fill rectangular area with solid color
Generic version for packed-pixel: cfb_fillrect
fb_copyarea - copy rectangular area
Generic version for packed-pixel: cfb_copyarea
>
> But the latest 2.6 fb_ops has removed these and
> there is entirely new set of functions.
> I tried to go to list archives but I could not find
> information.
> What functions in 2.6 fb_ops should to used to
> implement this old 2.4 set of functions?
Look at skeletonfb.c for comments. The simplest
framebuffer driver you can start with is vfb.c
Tony
next prev parent reply other threads:[~2006-06-12 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 12:26 porting fb driver to 2, 6(fb_get_fix, fb_get_var) syed khader
2006-06-12 12:44 ` Antonino A. Daplas [this message]
2006-06-20 12:01 ` syed khader
2006-06-20 14:25 ` Antonino A. Daplas
2006-06-21 7:37 ` syed khader
2006-06-21 8:41 ` 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=448D61C3.2070703@gmail.com \
--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.