From: "Robert Wörle" <rwoerle@mibtec.de>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Omapdss Managers confusion
Date: Wed, 16 Feb 2011 10:08:31 +0100 [thread overview]
Message-ID: <4D5B940F.8060101@mibtec.de> (raw)
In-Reply-To: <4D5B8C32.1070708@mibtec.de>
never mind ..
i think i found it .. my board code named my video device "tft" instead
of "lcd"
duhhh
sorry to bother anyone
Rob
Am 16.02.2011 09:34, schrieb Robert Wörle:
> Dear All
>
> May someon drop me a line about the following
>
> I am trying to run up a good gst pipeline ( to start with
> videotestsrc) but i am running into this
>
> My Device: igep0030 module
> my kernel: 2.6.35.9 from here (
> http://git.igep.es/?p=pub/scm/linux-omap-2.6.git;a=summary)
> cmdline is : omapfb.mode=lcd:1024x768MR@60 ubi.mtd=4 rootfstype=ubifs
> root=ubi0 console=ttyS0,115200n8 video=omapfb:vram:2M,vram:4M
> mem=88M@0x80000000 mem=384M@0x88000000
>
> All is compiled with openembedded.
>
> When i play this:
>
> root@biogas:~# DMAI_DEBUG=2 gst-launch --gst-debug=2 videotestsrc !
> TIDmaiVideo
> Sink autoselect=TRUE displayDevice=/dev/fb0 videoStd=VGA
> @0x000e8885:[T:0x402f2000] ti.sdo.dmai - [Dmai] Dmai log level set to
> '2'. Note that calling CERuntime_init after this point may cause
> unexpected change to DMAI tracing behavior.
> Setting pipeline to PAUSED ...
> Pipeline is PREROLLING ...
> Pipeline is PREROLLED ...
> Setting pipeline to PLAYING ...
> New clock: GstSystemClock
> @0x00104dc1:[T:0x4185a490] ti.sdo.dmai - [Buffer] Alloc Buffer of size
> 153600 at 0x419c7000 (0x868e7000 phys)
> @0x0010589a:[T:0x4185a490] ti.sdo.dmai - [Dmai] Unknown Device Output
> Found
> @0x001058f6:[T:0x4185a490] ti.sdo.dmai - [Dmai] Failed to Detect
> Current Display Output.
> @0x00105914:[T:0x4185a490] ti.sdo.dmai - [Dmai] Attempting to change to 3
> @0x00105951:[T:0x4185a490] ti.sdo.dmai - [Display] Failed to setup
> sysfs variables
> @0x00105a45:[T:0x4185a490] ti.sdo.dmai - [Dmai] Unknown Device Output
> Found
> @0x00105a64:[T:0x4185a490] ti.sdo.dmai - [Dmai] Failed to Detect
> Current Display Output.
> @0x00105a82:[T:0x4185a490] ti.sdo.dmai - [Dmai] Attempting to change to 3
>
> this loops till i stop the pipeline
>
>
> I followed the code into
> davinci_multimedia_application_interface/dmai/packages/ti/sdo/dmai/linux/omap3530/_Sysfs.c
>
> where it loops on working out the managers ( waiting for either "lcd"
> "tv" or "dvi")
>
> also
> kernel/drivers/video/omap2/dss/manager.c supports only "lcd" and "tv"
> as managers
> but my kernel shows
>
> root@biogas:~# cat /sys/devices/platform/omapdss/manager0/display
> tft
>
> So do i ve a miscombination of versions here ( one knowing about a new
> "tft" manager and one not ) ?
>
> All Documents i find never talk about "tft" , where is this coming from ?
>
> Any hints
>
> Thanks in advance
>
> Rob
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-16 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 8:34 Omapdss Managers confusion Robert Wörle
2011-02-16 9:08 ` Robert Wörle [this message]
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=4D5B940F.8060101@mibtec.de \
--to=rwoerle@mibtec.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox