public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Alex Gershgorin <alexg@meprolight.com>
Cc: "laurent.pinchart@ideasonboard.com"
	<laurent.pinchart@ideasonboard.com>,
	"Hiroshi.DOYU@nokia.com" <Hiroshi.DOYU@nokia.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: OMAP3ISP boot problem
Date: Sat, 10 Dec 2011 11:12:57 +0200	[thread overview]
Message-ID: <4EE32299.5000006@iki.fi> (raw)
In-Reply-To: <4875438356E7CA4A8F2145FCD3E61C0B2C89899244@MEP-EXCH.meprolight.com>

Alex Gershgorin wrote:
> Hi Sakari,
>
> Thank you for your quick response and sorry for stupid question.
> Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM  and CONFIG_OMAP_IOMMU.
> Please tell me how I can use dmabuf instead of the IOMMU/IOVMM API.

Unfortunately that real fix isn't available yet and won't be for some 
time. Still, it should be fully functional currently.

Looking at the backtrace again, it seems to crash in 
driver_find_device(). That looks fishy.

Do you have the ISP driver compiled into the kernel? I might try it as a 
module, albeit it of course should work when it's linked to the kernel 
as well.

-- 
Sakari Ailus
sakari.ailus@iki.fi

  reply	other threads:[~2011-12-10  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4875438356E7CA4A8F2145FCD3E61C0B2C8989923C@MEP-EXCH.meprolight.com>
2011-12-10  8:02 ` OMAP3ISP boot problem Alex Gershgorin
2011-12-10  8:23   ` Sakari Ailus
2011-12-10  8:53     ` Alex Gershgorin
2011-12-10  9:12       ` Sakari Ailus [this message]
2011-12-10 13:36         ` Alex Gershgorin
2011-12-10 14:45           ` Laurent Pinchart
2011-12-10 17:10             ` Alex Gershgorin
2011-12-11 10:56               ` Alex Gershgorin

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=4EE32299.5000006@iki.fi \
    --to=sakari.ailus@iki.fi \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=alexg@meprolight.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@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