* media0 not showing up on beagleboard-xm @ 2011-10-25 2:48 Chris Whittenburg 2011-11-04 11:49 ` Laurent Pinchart 0 siblings, 1 reply; 9+ messages in thread From: Chris Whittenburg @ 2011-10-25 2:48 UTC (permalink / raw) To: linux-media I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my beagleboard-xm. I'm interested in the media controller framework, which I believe is in this kernel. I expected there to be a /dev/media0, but it is not there. I do see "Linux media interface: v0.10" in my dmesg log, so I know media_devnode_init() is being called. Even without a sensor connected and camera defined, I should still get a media0 which represents the ISP, correct? I do have CONFIG_VIDEO_OMAP3=y in my kernel config. The only reference in the log that I see related to the isp is: omap-iommu omap-iommu.0: isp registered It looks like the kernel I'm using doesn't have support for the "camera=" cmdline option, so hopefully the presence of the camera is not required to kick things off. Thanks, Chris ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-10-25 2:48 media0 not showing up on beagleboard-xm Chris Whittenburg @ 2011-11-04 11:49 ` Laurent Pinchart 2011-11-06 22:26 ` Chris Whittenburg 0 siblings, 1 reply; 9+ messages in thread From: Laurent Pinchart @ 2011-11-04 11:49 UTC (permalink / raw) To: whittenburg; +Cc: linux-media Hi Chris, On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: > I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my > beagleboard-xm. > > I'm interested in the media controller framework, which I believe is > in this kernel. Yes it is. > I expected there to be a /dev/media0, but it is not there. I do see > "Linux media interface: v0.10" in my dmesg log, so I know > media_devnode_init() is being called. > > Even without a sensor connected and camera defined, I should still get > a media0 which represents the ISP, correct? I do have > CONFIG_VIDEO_OMAP3=y in my kernel config. The only reference in the > log that I see related to the isp is: > omap-iommu omap-iommu.0: isp registered > > It looks like the kernel I'm using doesn't have support for the > "camera=" cmdline option, so hopefully the presence of the camera is > not required to kick things off. You will need board code to register the OMAP3 ISP platform device that will then be picked by the OMAP3 ISP driver. Example of such board code can be found at http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb055e03b2ab15ccf6ad4befb8d -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-11-04 11:49 ` Laurent Pinchart @ 2011-11-06 22:26 ` Chris Whittenburg 2011-11-07 11:08 ` Gary Thomas 0 siblings, 1 reply; 9+ messages in thread From: Chris Whittenburg @ 2011-11-06 22:26 UTC (permalink / raw) To: Laurent Pinchart; +Cc: linux-media Hi Laurent, On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote: > Hi Chris, > > On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: >> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my >> beagleboard-xm. > > You will need board code to register the OMAP3 ISP platform device that will > then be picked by the OMAP3 ISP driver. Example of such board code can be > found at > > http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb055e03b2ab15ccf6ad4befb8d I followed your example to add the MT9P031 support, and now I get /dev/media0 and /dev/video0 to 7. I don't have the actual sensor hooked up yet. If I try "media-ctl -p", I see lots of "Failed to open subdev device node" msgs. http://pastebin.com/F1TC9A1n This is with the media-ctl utility from: http://feeds.angstrom-distribution.org/feeds/core/ipk/eglibc/armv7a/base/media-ctl_0.0.1-r0_armv7a.ipk I also tried with the latest from your media-ctl repository, but got the same msgs. Is this an issue with my 3.0.8 kernel not being compatible with current media-ctl utility? Is there some older commit that I should build from? Or maybe it is just a side effect of the sensor not being connected yet. thanks. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-11-06 22:26 ` Chris Whittenburg @ 2011-11-07 11:08 ` Gary Thomas 2011-11-07 11:14 ` Laurent Pinchart 0 siblings, 1 reply; 9+ messages in thread From: Gary Thomas @ 2011-11-07 11:08 UTC (permalink / raw) To: whittenburg; +Cc: Laurent Pinchart, linux-media On 2011-11-06 15:26, Chris Whittenburg wrote: > Hi Laurent, > > On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart > <laurent.pinchart@ideasonboard.com> wrote: >> Hi Chris, >> >> On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: >>> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my >>> beagleboard-xm. >> >> You will need board code to register the OMAP3 ISP platform device that will >> then be picked by the OMAP3 ISP driver. Example of such board code can be >> found at >> >> http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb055e03b2ab15ccf6ad4befb8d > > I followed your example to add the MT9P031 support, and now I get > /dev/media0 and /dev/video0 to 7. > > I don't have the actual sensor hooked up yet. > > If I try "media-ctl -p", I see lots of "Failed to open subdev device > node" msgs. > http://pastebin.com/F1TC9A1n > > This is with the media-ctl utility from: > http://feeds.angstrom-distribution.org/feeds/core/ipk/eglibc/armv7a/base/media-ctl_0.0.1-r0_armv7a.ipk > > I also tried with the latest from your media-ctl repository, but got > the same msgs. > > Is this an issue with my 3.0.8 kernel not being compatible with > current media-ctl utility? Is there some older commit that I should > build from? Or maybe it is just a side effect of the sensor not being > connected yet. Does your kernel config enable CONFIG_VIDEO_V4L2_SUBDEV_API? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-11-07 11:08 ` Gary Thomas @ 2011-11-07 11:14 ` Laurent Pinchart 2011-11-08 2:03 ` Chris Whittenburg 0 siblings, 1 reply; 9+ messages in thread From: Laurent Pinchart @ 2011-11-07 11:14 UTC (permalink / raw) To: Gary Thomas; +Cc: whittenburg, linux-media On Monday 07 November 2011 12:08:15 Gary Thomas wrote: > On 2011-11-06 15:26, Chris Whittenburg wrote: > > On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart wrote: > >> On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: > >>> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my > >>> beagleboard-xm. > >> > >> You will need board code to register the OMAP3 ISP platform device that > >> will then be picked by the OMAP3 ISP driver. Example of such board code > >> can be found at > >> > >> http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb055e03b > >> 2ab15ccf6ad4befb8d > > > > I followed your example to add the MT9P031 support, and now I get > > /dev/media0 and /dev/video0 to 7. > > > > I don't have the actual sensor hooked up yet. > > > > If I try "media-ctl -p", I see lots of "Failed to open subdev device > > node" msgs. > > http://pastebin.com/F1TC9A1n > > > > This is with the media-ctl utility from: > > http://feeds.angstrom-distribution.org/feeds/core/ipk/eglibc/armv7a/base/ > > media-ctl_0.0.1-r0_armv7a.ipk > > > > I also tried with the latest from your media-ctl repository, but got > > the same msgs. > > > > Is this an issue with my 3.0.8 kernel not being compatible with > > current media-ctl utility? Is there some older commit that I should > > build from? Or maybe it is just a side effect of the sensor not being > > connected yet. > > Does your kernel config enable CONFIG_VIDEO_V4L2_SUBDEV_API? And does your system run udev, or have you created the device nodes manually ? -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-11-07 11:14 ` Laurent Pinchart @ 2011-11-08 2:03 ` Chris Whittenburg 2011-11-08 12:42 ` Laurent Pinchart 0 siblings, 1 reply; 9+ messages in thread From: Chris Whittenburg @ 2011-11-08 2:03 UTC (permalink / raw) To: Laurent Pinchart; +Cc: Gary Thomas, linux-media On Mon, Nov 7, 2011 at 5:14 AM, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote: > On Monday 07 November 2011 12:08:15 Gary Thomas wrote: >> On 2011-11-06 15:26, Chris Whittenburg wrote: >> > On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart wrote: >> >> On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: >> >>> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my >> >>> beagleboard-xm. >> >> >> >> You will need board code to register the OMAP3 ISP platform device that >> >> will then be picked by the OMAP3 ISP driver. Example of such board code >> >> can be found at >> >> >> >> http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb055e03b >> >> 2ab15ccf6ad4befb8d >> > >> > I followed your example to add the MT9P031 support, and now I get >> > /dev/media0 and /dev/video0 to 7. >> > >> > I don't have the actual sensor hooked up yet. >> > >> > If I try "media-ctl -p", I see lots of "Failed to open subdev device >> > node" msgs. >> > http://pastebin.com/F1TC9A1n >> > >> > This is with the media-ctl utility from: >> > http://feeds.angstrom-distribution.org/feeds/core/ipk/eglibc/armv7a/base/ >> > media-ctl_0.0.1-r0_armv7a.ipk >> > >> > I also tried with the latest from your media-ctl repository, but got >> > the same msgs. >> > >> > Is this an issue with my 3.0.8 kernel not being compatible with >> > current media-ctl utility? Is there some older commit that I should >> > build from? Or maybe it is just a side effect of the sensor not being >> > connected yet. >> >> Does your kernel config enable CONFIG_VIDEO_V4L2_SUBDEV_API? Yes, it is enabled... Here is a snippet of my config: # # Multimedia core support # CONFIG_MEDIA_CONTROLLER=y CONFIG_VIDEO_DEV=y CONFIG_VIDEO_V4L2_COMMON=y CONFIG_VIDEO_V4L2_SUBDEV_API=y CONFIG_DVB_CORE=m CONFIG_VIDEO_MEDIA=m > And does your system run udev, or have you created the device nodes manually ? It runs udev-173... I didn't create the nodes manually. I also have the /dev/v4l-subdev0 to 7 entries, as expected. Anything else I should check? Thanks. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-11-08 2:03 ` Chris Whittenburg @ 2011-11-08 12:42 ` Laurent Pinchart 2011-11-09 2:53 ` Chris Whittenburg 0 siblings, 1 reply; 9+ messages in thread From: Laurent Pinchart @ 2011-11-08 12:42 UTC (permalink / raw) To: whittenburg; +Cc: Gary Thomas, linux-media Hi Chris, On Tuesday 08 November 2011 03:03:43 Chris Whittenburg wrote: > On Mon, Nov 7, 2011 at 5:14 AM, Laurent Pinchart wrote: > > On Monday 07 November 2011 12:08:15 Gary Thomas wrote: > >> On 2011-11-06 15:26, Chris Whittenburg wrote: > >> > On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart wrote: > >> >> On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: > >> >>> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my > >> >>> beagleboard-xm. > >> >> > >> >> You will need board code to register the OMAP3 ISP platform device > >> >> that will then be picked by the OMAP3 ISP driver. Example of such > >> >> board code can be found at > >> >> > >> >> http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb055e > >> >> 03b 2ab15ccf6ad4befb8d > >> > > >> > I followed your example to add the MT9P031 support, and now I get > >> > /dev/media0 and /dev/video0 to 7. > >> > > >> > I don't have the actual sensor hooked up yet. > >> > > >> > If I try "media-ctl -p", I see lots of "Failed to open subdev device > >> > node" msgs. > >> > http://pastebin.com/F1TC9A1n > >> > > >> > This is with the media-ctl utility from: > >> > http://feeds.angstrom-distribution.org/feeds/core/ipk/eglibc/armv7a/ba > >> > se/ media-ctl_0.0.1-r0_armv7a.ipk > >> > > >> > I also tried with the latest from your media-ctl repository, but got > >> > the same msgs. > >> > > >> > Is this an issue with my 3.0.8 kernel not being compatible with > >> > current media-ctl utility? Is there some older commit that I should > >> > build from? Or maybe it is just a side effect of the sensor not being > >> > connected yet. > >> > >> Does your kernel config enable CONFIG_VIDEO_V4L2_SUBDEV_API? > > Yes, it is enabled... Here is a snippet of my config: > > # > # Multimedia core support > # > CONFIG_MEDIA_CONTROLLER=y > CONFIG_VIDEO_DEV=y > CONFIG_VIDEO_V4L2_COMMON=y > CONFIG_VIDEO_V4L2_SUBDEV_API=y > CONFIG_DVB_CORE=m > CONFIG_VIDEO_MEDIA=m > > > And does your system run udev, or have you created the device nodes > > manually ? > > It runs udev-173... I didn't create the nodes manually. > > I also have the /dev/v4l-subdev0 to 7 entries, as expected. > > Anything else I should check? Could you please send me the output of the following commands ? ls -l /dev/v4l-subdev* ls -l /sys/dev/char/ And, optionally, strace ./media-ctl -p -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-11-08 12:42 ` Laurent Pinchart @ 2011-11-09 2:53 ` Chris Whittenburg 2011-11-09 9:21 ` Laurent Pinchart 0 siblings, 1 reply; 9+ messages in thread From: Chris Whittenburg @ 2011-11-09 2:53 UTC (permalink / raw) To: Laurent Pinchart; +Cc: Gary Thomas, linux-media On Tue, Nov 8, 2011 at 6:42 AM, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote: > Hi Chris, > > On Tuesday 08 November 2011 03:03:43 Chris Whittenburg wrote: >> On Mon, Nov 7, 2011 at 5:14 AM, Laurent Pinchart wrote: >> > On Monday 07 November 2011 12:08:15 Gary Thomas wrote: >> >> On 2011-11-06 15:26, Chris Whittenburg wrote: >> >> > On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart wrote: >> >> >> On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: >> >> >>> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my >> >> >>> beagleboard-xm. >> >> >> >> >> >> You will need board code to register the OMAP3 ISP platform device >> >> >> that will then be picked by the OMAP3 ISP driver. Example of such >> >> >> board code can be found at >> >> >> >> >> >> http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb055e >> >> >> 03b 2ab15ccf6ad4befb8d >> >> > >> >> > I followed your example to add the MT9P031 support, and now I get >> >> > /dev/media0 and /dev/video0 to 7. >> >> > >> >> > I don't have the actual sensor hooked up yet. >> >> > >> >> > If I try "media-ctl -p", I see lots of "Failed to open subdev device >> >> > node" msgs. >> >> > http://pastebin.com/F1TC9A1n >> >> > >> >> > This is with the media-ctl utility from: >> >> > http://feeds.angstrom-distribution.org/feeds/core/ipk/eglibc/armv7a/ba >> >> > se/ media-ctl_0.0.1-r0_armv7a.ipk >> >> > >> >> > I also tried with the latest from your media-ctl repository, but got >> >> > the same msgs. >> >> > >> >> > Is this an issue with my 3.0.8 kernel not being compatible with >> >> > current media-ctl utility? Is there some older commit that I should >> >> > build from? Or maybe it is just a side effect of the sensor not being >> >> > connected yet. >> >> >> >> Does your kernel config enable CONFIG_VIDEO_V4L2_SUBDEV_API? >> >> Yes, it is enabled... Here is a snippet of my config: >> >> # >> # Multimedia core support >> # >> CONFIG_MEDIA_CONTROLLER=y >> CONFIG_VIDEO_DEV=y >> CONFIG_VIDEO_V4L2_COMMON=y >> CONFIG_VIDEO_V4L2_SUBDEV_API=y >> CONFIG_DVB_CORE=m >> CONFIG_VIDEO_MEDIA=m >> >> > And does your system run udev, or have you created the device nodes >> > manually ? >> >> It runs udev-173... I didn't create the nodes manually. >> >> I also have the /dev/v4l-subdev0 to 7 entries, as expected. >> >> Anything else I should check? > > Could you please send me the output of the following commands ? > > ls -l /dev/v4l-subdev* > ls -l /sys/dev/char/ > > And, optionally, > > strace ./media-ctl -p Hi Laurent, Your last questions helped me find that sysfs wasn't mounted. I think this is because meta-Angstrom was using systemd, and I changed it to sysvinit, but must have missed something. With sysfs mounted, I get the following media-ctl -p output... Does this look as expected? (The sensor still isn't connected-- it should come in today, so ignore the "Failed to reset the camera" errors. root@beagleboard:~# media-ctl -p Opening media device /dev/media0 Enumerating entities Found 16 entities Enumerating pads and links Device topology - entity 1: OMAP3 ISP CCP2 (2 pads, 2 links) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev0 pad0: Input [SGRBG10 4096x4096] <- 'OMAP3 ISP CCP2 input':pad0 [] pad1: Output [SGRBG10 4096x4096] -> 'OMAP3 ISP CCDC':pad0 [] - entity 2: OMAP3 ISP CCP2 input (1 pad, 1 link) type Node subtype V4L device node name /dev/video0 pad0: Output -> 'OMAP3 ISP CCP2':pad0 [] - entity 3: OMAP3 ISP CSI2a (2 pads, 2 links) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev1 pad0: Input [SGRBG10 4096x4096] pad1: Output [SGRBG10 4096x4096] -> 'OMAP3 ISP CSI2a output':pad0 [] -> 'OMAP3 ISP CCDC':pad0 [] - entity 4: OMAP3 ISP CSI2a output (1 pad, 1 link) type Node subtype V4L device node name /dev/video1 pad0: Input <- 'OMAP3 ISP CSI2a':pad1 [] - entity 5: OMAP3 ISP CCDC (3 pads, 9 links) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev2 pad0: Input [SGRBG10 4096x4096] <- 'OMAP3 ISP CCP2':pad1 [] <- 'OMAP3 ISP CSI2a':pad1 [] <- 'mt9p031 2-0048':pad0 [] pad1: Output [SGRBG10 4096x4096] -> 'OMAP3 ISP CCDC output':pad0 [] -> 'OMAP3 ISP resizer':pad0 [] pad2: Output [SGRBG10 4096x4095] -> 'OMAP3 ISP preview':pad0 [] -> 'OMAP3 ISP AEWB':pad0 [IMMUTABLE,ACTIVE] -> 'OMAP3 ISP AF':pad0 [IMMUTABLE,ACTIVE] -> 'OMAP3 ISP histogram':pad0 [IMMUTABLE,ACTIVE] - entity 6: OMAP3 ISP CCDC output (1 pad, 1 link) type Node subtype V4L device node name /dev/video2 pad0: Input <- 'OMAP3 ISP CCDC':pad1 [] - entity 7: OMAP3 ISP preview (2 pads, 4 links) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev3 pad0: Input [SGRBG10 4096x4096] <- 'OMAP3 ISP CCDC':pad2 [] <- 'OMAP3 ISP preview input':pad0 [] pad1: Output [YUYV 4082x4088] -> 'OMAP3 ISP preview output':pad0 [] -> 'OMAP3 ISP resizer':pad0 [] - entity 8: OMAP3 ISP preview input (1 pad, 1 link) type Node subtype V4L device node name /dev/video3 pad0: Output -> 'OMAP3 ISP preview':pad0 [] - entity 9: OMAP3 ISP preview output (1 pad, 1 link) type Node subtype V4L device node name /dev/video4 pad0: Input <- 'OMAP3 ISP preview':pad1 [] - entity 10: OMAP3 ISP resizer (2 pads, 4 links) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev4 pad0: Input [YUYV 4095x4095 (4,6)/4086x4082] <- 'OMAP3 ISP CCDC':pad1 [] <- 'OMAP3 ISP preview':pad1 [] <- 'OMAP3 ISP resizer input':pad0 [] pad1: Output [YUYV 4096x4095] -> 'OMAP3 ISP resizer output':pad0 [] - entity 11: OMAP3 ISP resizer input (1 pad, 1 link) type Node subtype V4L device node name /dev/video5 pad0: Output -> 'OMAP3 ISP resizer':pad0 [] - entity 12: OMAP3 ISP resizer output (1 pad, 1 link) type Node subtype V4L device node name /dev/video6 pad0: Input <- 'OMAP3 ISP resizer':pad1 [] - entity 13: OMAP3 ISP AEWB (1 pad, 1 link) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev5 pad0: Input <- 'OMAP3 ISP CCDC':pad2 [IMMUTABLE,ACTIVE] - entity 14: OMAP3 ISP AF (1 pad, 1 link) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev6 pad0: Input <- 'OMAP3 ISP CCDC':pad2 [IMMUTABLE,ACTIVE] - entity 15: OMAP3 ISP histogram (1 pad, 1 link) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev7 pad0: Input <- 'OMAP3 ISP CCDC':pad2 [IMMUTABLE,ACTIVE] - entity 16: mt9p031 2-0048 (1 pad, 1 link) type V4L2 subdev subtype Unknown device node name /dev/v4l-subdev8 pad0: Output v4l2_subdev_open: Failed to open subdev device node /dev/v4l-subdev8 -> 'OMAP3 ISP CCDC':pad0 [] Thanks. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: media0 not showing up on beagleboard-xm 2011-11-09 2:53 ` Chris Whittenburg @ 2011-11-09 9:21 ` Laurent Pinchart 0 siblings, 0 replies; 9+ messages in thread From: Laurent Pinchart @ 2011-11-09 9:21 UTC (permalink / raw) To: whittenburg; +Cc: Gary Thomas, linux-media Hi Chris, On Wednesday 09 November 2011 03:53:58 Chris Whittenburg wrote: > On Tue, Nov 8, 2011 at 6:42 AM, Laurent Pinchart wrote: > > On Tuesday 08 November 2011 03:03:43 Chris Whittenburg wrote: > >> On Mon, Nov 7, 2011 at 5:14 AM, Laurent Pinchart wrote: > >> > On Monday 07 November 2011 12:08:15 Gary Thomas wrote: > >> >> On 2011-11-06 15:26, Chris Whittenburg wrote: > >> >> > On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart wrote: > >> >> >> On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote: > >> >> >>> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on > >> >> >>> my beagleboard-xm. > >> >> >> > >> >> >> You will need board code to register the OMAP3 ISP platform device > >> >> >> that will then be picked by the OMAP3 ISP driver. Example of such > >> >> >> board code can be found at > >> >> >> > >> >> >> http://git.linuxtv.org/pinchartl/media.git/commit/37f505296ccd3fb0 > >> >> >> 55e 03b 2ab15ccf6ad4befb8d > >> >> > > >> >> > I followed your example to add the MT9P031 support, and now I get > >> >> > /dev/media0 and /dev/video0 to 7. > >> >> > > >> >> > I don't have the actual sensor hooked up yet. > >> >> > > >> >> > If I try "media-ctl -p", I see lots of "Failed to open subdev > >> >> > device node" msgs. > >> >> > http://pastebin.com/F1TC9A1n > >> >> > > >> >> > This is with the media-ctl utility from: > >> >> > http://feeds.angstrom-distribution.org/feeds/core/ipk/eglibc/armv7a > >> >> > /ba se/ media-ctl_0.0.1-r0_armv7a.ipk > >> >> > > >> >> > I also tried with the latest from your media-ctl repository, but > >> >> > got the same msgs. > >> >> > > >> >> > Is this an issue with my 3.0.8 kernel not being compatible with > >> >> > current media-ctl utility? Is there some older commit that I > >> >> > should build from? Or maybe it is just a side effect of the > >> >> > sensor not being connected yet. > >> >> > >> >> Does your kernel config enable CONFIG_VIDEO_V4L2_SUBDEV_API? > >> > >> Yes, it is enabled... Here is a snippet of my config: > >> > >> # > >> # Multimedia core support > >> # > >> CONFIG_MEDIA_CONTROLLER=y > >> CONFIG_VIDEO_DEV=y > >> CONFIG_VIDEO_V4L2_COMMON=y > >> CONFIG_VIDEO_V4L2_SUBDEV_API=y > >> CONFIG_DVB_CORE=m > >> CONFIG_VIDEO_MEDIA=m > >> > >> > And does your system run udev, or have you created the device nodes > >> > manually ? > >> > >> It runs udev-173... I didn't create the nodes manually. > >> > >> I also have the /dev/v4l-subdev0 to 7 entries, as expected. > >> > >> Anything else I should check? > > > > Could you please send me the output of the following commands ? > > > > ls -l /dev/v4l-subdev* > > ls -l /sys/dev/char/ > > > > And, optionally, > > > > strace ./media-ctl -p > > Hi Laurent, > > Your last questions helped me find that sysfs wasn't mounted. I think > this is because meta-Angstrom was using systemd, and I changed it to > sysvinit, but must have missed something. > > With sysfs mounted, I get the following media-ctl -p output... Does > this look as expected? (The sensor still isn't connected-- it should > come in today, so ignore the "Failed to reset the camera" errors. Yes, the media-ctl -p output looks correct. > root@beagleboard:~# media-ctl -p > Opening media device /dev/media0 > Enumerating entities > Found 16 entities > Enumerating pads and links > Device topology > - entity 1: OMAP3 ISP CCP2 (2 pads, 2 links) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev0 > pad0: Input [SGRBG10 4096x4096] > <- 'OMAP3 ISP CCP2 input':pad0 [] > pad1: Output [SGRBG10 4096x4096] > -> 'OMAP3 ISP CCDC':pad0 [] > > - entity 2: OMAP3 ISP CCP2 input (1 pad, 1 link) > type Node subtype V4L > device node name /dev/video0 > pad0: Output > -> 'OMAP3 ISP CCP2':pad0 [] > > - entity 3: OMAP3 ISP CSI2a (2 pads, 2 links) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev1 > pad0: Input [SGRBG10 4096x4096] > pad1: Output [SGRBG10 4096x4096] > -> 'OMAP3 ISP CSI2a output':pad0 [] > -> 'OMAP3 ISP CCDC':pad0 [] > > - entity 4: OMAP3 ISP CSI2a output (1 pad, 1 link) > type Node subtype V4L > device node name /dev/video1 > pad0: Input > <- 'OMAP3 ISP CSI2a':pad1 [] > > - entity 5: OMAP3 ISP CCDC (3 pads, 9 links) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev2 > pad0: Input [SGRBG10 4096x4096] > <- 'OMAP3 ISP CCP2':pad1 [] > <- 'OMAP3 ISP CSI2a':pad1 [] > <- 'mt9p031 2-0048':pad0 [] > pad1: Output [SGRBG10 4096x4096] > -> 'OMAP3 ISP CCDC output':pad0 [] > -> 'OMAP3 ISP resizer':pad0 [] > pad2: Output [SGRBG10 4096x4095] > -> 'OMAP3 ISP preview':pad0 [] > -> 'OMAP3 ISP AEWB':pad0 [IMMUTABLE,ACTIVE] > -> 'OMAP3 ISP AF':pad0 [IMMUTABLE,ACTIVE] > -> 'OMAP3 ISP histogram':pad0 [IMMUTABLE,ACTIVE] > > - entity 6: OMAP3 ISP CCDC output (1 pad, 1 link) > type Node subtype V4L > device node name /dev/video2 > pad0: Input > <- 'OMAP3 ISP CCDC':pad1 [] > > - entity 7: OMAP3 ISP preview (2 pads, 4 links) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev3 > pad0: Input [SGRBG10 4096x4096] > <- 'OMAP3 ISP CCDC':pad2 [] > <- 'OMAP3 ISP preview input':pad0 [] > pad1: Output [YUYV 4082x4088] > -> 'OMAP3 ISP preview output':pad0 [] > -> 'OMAP3 ISP resizer':pad0 [] > > - entity 8: OMAP3 ISP preview input (1 pad, 1 link) > type Node subtype V4L > device node name /dev/video3 > pad0: Output > -> 'OMAP3 ISP preview':pad0 [] > > - entity 9: OMAP3 ISP preview output (1 pad, 1 link) > type Node subtype V4L > device node name /dev/video4 > pad0: Input > <- 'OMAP3 ISP preview':pad1 [] > > - entity 10: OMAP3 ISP resizer (2 pads, 4 links) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev4 > pad0: Input [YUYV 4095x4095 (4,6)/4086x4082] > <- 'OMAP3 ISP CCDC':pad1 [] > <- 'OMAP3 ISP preview':pad1 [] > <- 'OMAP3 ISP resizer input':pad0 [] > pad1: Output [YUYV 4096x4095] > -> 'OMAP3 ISP resizer output':pad0 [] > > - entity 11: OMAP3 ISP resizer input (1 pad, 1 link) > type Node subtype V4L > device node name /dev/video5 > pad0: Output > -> 'OMAP3 ISP resizer':pad0 [] > > - entity 12: OMAP3 ISP resizer output (1 pad, 1 link) > type Node subtype V4L > device node name /dev/video6 > pad0: Input > <- 'OMAP3 ISP resizer':pad1 [] > > - entity 13: OMAP3 ISP AEWB (1 pad, 1 link) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev5 > pad0: Input > <- 'OMAP3 ISP CCDC':pad2 [IMMUTABLE,ACTIVE] > > - entity 14: OMAP3 ISP AF (1 pad, 1 link) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev6 > pad0: Input > <- 'OMAP3 ISP CCDC':pad2 [IMMUTABLE,ACTIVE] > > - entity 15: OMAP3 ISP histogram (1 pad, 1 link) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev7 > pad0: Input > <- 'OMAP3 ISP CCDC':pad2 [IMMUTABLE,ACTIVE] > > - entity 16: mt9p031 2-0048 (1 pad, 1 link) > type V4L2 subdev subtype Unknown > device node name /dev/v4l-subdev8 > pad0: Output v4l2_subdev_open: Failed to open subdev device node > /dev/v4l-subdev8 > > -> 'OMAP3 ISP CCDC':pad0 [] > > Thanks. -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2011-11-09 9:21 UTC | newest] Thread overview: 9+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-10-25 2:48 media0 not showing up on beagleboard-xm Chris Whittenburg 2011-11-04 11:49 ` Laurent Pinchart 2011-11-06 22:26 ` Chris Whittenburg 2011-11-07 11:08 ` Gary Thomas 2011-11-07 11:14 ` Laurent Pinchart 2011-11-08 2:03 ` Chris Whittenburg 2011-11-08 12:42 ` Laurent Pinchart 2011-11-09 2:53 ` Chris Whittenburg 2011-11-09 9:21 ` Laurent Pinchart
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.