From: LD <memorylost@tin.it>
To: Linux ppc mailing list <linuxppc-dev@lists.ozlabs.org>,
Lucio Dona' <memorylost@tin.it>
Subject: MPC5121e DIU driver - kernel crash writing alpha component
Date: Fri, 23 Oct 2009 09:16:46 +0200 [thread overview]
Message-ID: <4AE1585E.60002@tin.it> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I am working on Freescale MPC5121e evaluation board ADS512101 rev. 3 (M34K
processor stepping), developing a graphical application.
Just switched to ADS512101 rev. 4, 0M36P processor stepping.
I have problems with the video framebuffer driver, try to explain:
- - app is based on microwindows+fltk, framebuffer driver. On rev3 board working ok.
- - rev4 board: using the kernel from ltib 2009/06/02, just adapted fsl-diu-fb.c
and .h to support resolution and timings of my lcd panel.
The board is booting ok (NFS), but my user space app keeps crashing the kernel.
I noticed that in 0M36P processor stepping there are many changes about the
video interface (DIU), correcting some bugs of the previous stepping ; seems
that when I write to the ram area which is mapped to Panel0 of the DIU the
system randomly hangs.
After some debugging...
800x480, 32 bits per pixel, using plane1 (first plane, as described in the
processor's reference manual).
If, from user space, I write some alpha component != 0 in this plane then I have
a complete system crash.
The reference pdf says "There is no alpha component defined for plane1 because
there are no planes behind it."
I did not yet investigate about writing in other planes ; time is short...
For now, patched microwindows driver for writing 0x00 in alpha components, no
more hangs.
Reported to Freescale FAE, waiting for some answers.
Meanwhile: some suggestions about filtering alpha components in the video driver ?
I was thinking about some sort of double buffering : user space app
(fltk--->microwindows) writes in a buffer,
then the driver clears alpha to 0x00 and memcpy to the real video buffer.
Problems:
- - driver / user space sync. Vertical retrace ? ioctl ?
- - waste of memory, needs double video buffers
Any suggestions are welcome,
work in progress.
Regards
Lucio Dona'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFK4VhdvxHCsvXy9okRAtrtAKCaAectSfrHOfzcbTR7KfF9lHCY1QCeOcND
HC9fMyGUATKeDL9z9IEzAWc=
=ofjv
-----END PGP SIGNATURE-----
next reply other threads:[~2009-10-23 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 7:16 LD [this message]
2009-10-23 8:46 ` MPC5121e DIU driver - kernel crash writing alpha component Chen Hongjun-R66092
2009-10-23 9:59 ` LD
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=4AE1585E.60002@tin.it \
--to=memorylost@tin.it \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).