From: Gary Thomas <gary@mlbassoc.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: DSS: OMAP3530 vs DM3730
Date: Sat, 21 Jan 2012 09:16:38 -0700 [thread overview]
Message-ID: <4F1AE4E6.8090000@mlbassoc.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
I'm running the public 3.0 kernel on my boards. I have some boards
which can have either OMAP3530 or DM3730 (newer boards have the
newer part, but everything else is the same).
On the OMAP3530, I can enable the graphics overlay on the TV (S-Video)
output via the attached script. On the DM3730 boards, this crashes
the kernel hard :-(
This same operation seems to be fixed on the 3.2 (public) kernel, but
it's difficult for me to upgrade to that kernel for some other reasons.
Does anyone have an idea why this might happen? where to look to
isolate the bug(s)?
I tried to back-port the 3.2 DSS code into my 3.0 kernel, but my
simple attempt was pretty much a failure... If I can, I'd like to
figure out how to just fix the 3.0 code, rather than the full-scale
import of the 3.2 code.
Thanks for any ideas/pointers
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
[-- Attachment #2: tv_video --]
[-- Type: text/plain, Size: 982 bytes --]
#! /bin/sh
#
# This script will put the TV (S-Video) into graphics mode,
# mapped onto /dev/fb2
#
ovl0=/sys/devices/platform/omapdss/overlay0
ovl1=/sys/devices/platform/omapdss/overlay1
ovl2=/sys/devices/platform/omapdss/overlay2
mgr0=/sys/devices/platform/omapdss/manager0
mgr1=/sys/devices/platform/omapdss/manager1
lcd=/sys/devices/platform/omapdss/display0
tv=/sys/devices/platform/omapdss/display1
fb0=/sys/class/graphics/fb0
fb1=/sys/class/graphics/fb1
fb2=/sys/class/graphics/fb2
#MODE=${MODE:-ntsc}
MODE=${MODE:-pal}
echo "0" > $tv/enabled
echo ${MODE} >$tv/timings
w=`cat $tv/timings | cut -d "," -f 2 | cut -d "/" -f 1`
h=`cat $tv/timings | cut -d "," -f 3 | cut -d "/" -f 1`
echo "... Setting ${MODE} mode, Width = ${w}, Height = ${h}"
echo "0" > $ovl2/enabled
echo "2" > $fb2/overlays
echo "$w,$h" > $ovl2/output_size
echo "tv" > $ovl2/manager
mem=$((w*h*4))
echo $mem > $fb2/size
echo "1" > $ovl2/enabled
echo "1" > $tv/enabled
fbset -fb /dev/fb2 -nonstd 1
next reply other threads:[~2012-01-21 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 16:16 Gary Thomas [this message]
2012-01-23 5:06 ` OMAP3530 vs DM3730 Hiremath, Vaibhav
2012-01-23 13:46 ` Gary Thomas
2012-01-25 11:07 ` Tomi Valkeinen
2012-01-25 12:24 ` Gary Thomas
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=4F1AE4E6.8090000@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linux-omap@vger.kernel.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 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.