public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: linux-omap@vger.kernel.org
Subject: OMAP TV video
Date: Wed, 04 Feb 2009 07:57:37 -0700	[thread overview]
Message-ID: <4989ACE1.7050409@mlbassoc.com> (raw)

Note: if this is the wrong list, or if there's a better place
to ask these questions, please redirect me.

I have an OMAP/Zoom1 (3430 LDP).  I'm trying to use the
S-Video output, without much success.  Today, I grabbed
the latest tree (as least from what I can gather from various
web pages) from git://git.omapzoom.org/repo/omapkernel.git

When I try to use the TV, the kernel crashes immediately:
Unhandled fault: external abort on non-linefetch (0x1008) at 0xd8050440
Internal error: : 1008 [#1]
Modules linked in:

CPU: 0    Not tainted  (2.6.27.10-omap1-00181-gc9fd795 #1)
PC is at omap2_disp_enable_output_dev+0x30/0x44
LR is at write_layer_out+0x118/0x220
pc : [<c0053a84>]    lr : [<c018f3d4>]    psr: 60000013
sp : c7963ec8  ip : c7963ed8  fp : c7963ed4
r10: c7963f70  r9 : c7940e78  r8 : c039c8f0
r7 : 00000000  r6 : 00000003  r5 : c78626f8  r4 : c03c3c44
r3 : 00000000  r2 : d8050000  r1 : 00000003  r0 : 00000005
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 00c5387f  Table: 87320018  DAC: 00000015
Process echo (pid: 723, stack limit = 0xc79622e0)

kernel version: Linux version 2.6.27.10-omap1-00181-gc9fd795
config: omap_ldp_defconfig

Notes:
* An older kernel (circa 2008-12-01) does not crash.  The
  TV output is not correct, but at least it doesn't crash.
* How can I turn off the double printk()?  All kernel messages
  get duplicated and it makes it terribly hard to use.  e.g.

    <5>Looking up port of RPC 100003/2 on 192.168.1.100
    Looking up port of RPC 100003/2 on 192.168.1.100
    <5>Looking up port of RPC 100005/1 on 192.168.1.100
    Looking up port of RPC 100005/1 on 192.168.1.100
    VFS: Mounted root (nfs filesystem).
    VFS: Mounted root (nfs filesystem).

  Other kernels (PowerPC, etc) don't suffer from this.
* This kernel version is very unstable - it simply quits after
  just a few moments of running.  I didn't see this with the
  older kernel.

Thanks for any ideas/pointers

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

             reply	other threads:[~2009-02-04 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 14:57 Gary Thomas [this message]
2009-02-04 15:15 ` OMAP TV video Imre Deak
2009-02-04 15:33   ` Gary Thomas
2009-02-04 22:07     ` Gary Thomas
  -- strict thread matches above, loose matches on Subject: below --
2009-02-10 16:05 OMAP [TV] video Gary Thomas
2009-02-11  4:12 ` Hiremath, Vaibhav
2009-02-11 12:25   ` Gary Thomas
2009-02-11 13:04     ` Koen Kooi

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=4989ACE1.7050409@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox