From: James Simmons <jsimmons@infradead.org>
To: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Cc: Aitor Garcia <carrierphasejitter@yahoo.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: enquiry about 4 bpp frame buffer with nibbles swapped
Date: Wed, 21 Feb 2007 21:50:22 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0702212148500.20620@pentafluge.infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0702210832300.7944@pademelon.sonytel.be>
> > But I do not know where to do it.
> > Frame Buffer has 3 functions cfb_fillrect,
> > cfb_copyarea and cfb_imageblit which I thought were
> > the key to solve my problems but Qtopia Core does not
> > make use
> > of them.
>
> Indeed, cfb_{fillrect,copyarea,imageblit}() are used by the kernel only.
Speaking of. Are you using fbcon? If that is the case then your console
should look messed up.
> > imxfb_map_video_memory function or fb_mmap, seem to be
> > good candidates but I do not know how to progress
> > further.
>
> If the order of the nibbles can be configured in hardware, you should do that.
> Else I'm afraid you will have to modify Qtopia Core.
Can fb_bitfield handle that case ?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-02-21 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 12:11 enquiry about 4 bpp frame buffer with nibbles swapped Aitor Garcia
2007-02-21 7:34 ` Geert Uytterhoeven
2007-02-21 21:50 ` James Simmons [this message]
2007-02-22 8:08 ` Geert Uytterhoeven
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=Pine.LNX.4.64.0702212148500.20620@pentafluge.infradead.org \
--to=jsimmons@infradead.org \
--cc=carrierphasejitter@yahoo.com \
--cc=geert@linux-m68k.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 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.