From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Julien Lebot <lesnip3r@hotmail.com>
Subject: Re: PXA270 framebuffer
Date: Thu, 07 Jun 2007 21:52:13 +0800 [thread overview]
Message-ID: <1181224333.4502.20.camel@daplas> (raw)
In-Reply-To: <BAY112-F36C82E4DE08DC1A472621A83260@phx.gbl>
On Thu, 2007-06-07 at 15:22 +0400, Julien Lebot wrote:
> Hi,
>
> I'm currently developping on the Gumstix verdex platform and I noticed that
> the PXA270 processor includes a support for smartpanel screen in its
> framebuffer.
>
> I've already written a small "driver" which is just a prototype to test if
> the LCD panel was working but it's far from being something really useful.
> (display only a picture, call some hardware functions of the LCD (rotate
> ...) and exit)
> Also it's not using the PXA270 framebuffer at all, the communication
> protocol is handled in software which is pretty slow (about 1sec to display
> the picture).
>
> Since the PXA270 uses the pxafb driver I wonder is there is any plan to add
> the support for smart panels.
> I thought about modifying the driver so that parameters can be passed at
> boot time specifying if it is a smart-panel or a "regular" LCD along with
> other video parameters.
> In the driver I understand that it is needed to set up the framebuffer
> registers, then enabling the framebuffer and passing the data/command
> through the DMA channel 6 using some kind of scheduling function.
> Well so far all my attempts did not lead to something viable :D
>
> I've also tried to write a framebuffer driver from vfb and fbskeleton for
> this kind of screen but I'm a real newbie at kernel programming, thus
> leading to nothing at the moment.
> I've posted on the linux-kernel mailing list and got some useful answers
> about kernel programming and the framebuffer itself, though I think this
> mailing list is more appropriate.
>
> Any idea / help would be really appreciated,
You may want to look at arcfb.c. If you look at it's copyarea, fillrect
and imageblit functions, they use the generic drawing functions, then
immediately followed by an arcfb_lcd_update(). That's where the contents
of the framebuffer is transferred to the internal memory of the LCD.
The same is done for arcfb_write().
(You may want to do this step first.)
The above method make the framebuffer console work. Writing to /dev/fb0
will also work (cat "file" > /dev/fb0). However, for applications that
uses mmap(), such as X, it will not work. You have to do some VM magic
to make mmap() function for your driver. For this functionality, look at
hecubafb.c driver and fb_defio.c. hecubafb.c and fb_defio.c is new for
2.6.21.
(This is the second step to make your smart lcd fully functional.)
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-06-07 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 11:22 PXA270 framebuffer Julien Lebot
2007-06-07 13:52 ` Antonino A. Daplas [this message]
2007-06-09 7:04 ` Julien Lebot
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=1181224333.4502.20.camel@daplas \
--to=adaplas@gmail.com \
--cc=lesnip3r@hotmail.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 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).