From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Alex Gershgorin <alexg@meprolight.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
"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 15:45:38 +0100 [thread overview]
Message-ID: <201112101545.40059.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <4875438356E7CA4A8F2145FCD3E61C0B2C89899246@MEP-EXCH.meprolight.com>
Hi Alex,
On Saturday 10 December 2011 14:36:17 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.
>
> Yes ISP driver compiled into kernel, but if I back to previos version of
> the Linux kernel 3.0.0, that works well. Here part of kernel boot
> message...
>
> > [ 2.063354] Linux media interface: v0.10
> > [ 2.068298] Linux video capture interface: v2.00
> > [ 2.075561] omap3isp omap3isp: Revision 2.0 found
> > [ 2.080932] omap-iommu omap-iommu.0: isp: version 1.1
> > [ 2.099365] Camera Video probed
> > [ 2.115997] vivi-000: V4L2 device registered as video7
>
> Now I plan to start using a newer version of the Linux kernel 3.2.0-rc4,
> but unfortunately faced with the problem. That suggest?
I'm quite surprised. I've just tested 3.2-rc2 here, and got no oops when
loading the omap3-isp driver. I've tried compiling the driver in the kernel
and as a module, and both succeeded. I've pushed my code to
http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
sensors-board if you want to give it a try.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2011-12-10 14:45 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
2011-12-10 13:36 ` Alex Gershgorin
2011-12-10 14:45 ` Laurent Pinchart [this message]
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=201112101545.40059.laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=alexg@meprolight.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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