All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] Adding YUV input support for OMAP3ISP driver
Date: Thu, 19 Jan 2012 05:41:57 -0700	[thread overview]
Message-ID: <4F180F95.7050003@mlbassoc.com> (raw)
In-Reply-To: <201201171633.50619.laurent.pinchart@ideasonboard.com>

On 2012-01-17 08:33, Laurent Pinchart wrote:
    <snip>
>
> I already had a couple of YUV support patches in my OMAP3 ISP tree at
> git.kernel.org. I've rebased them on top of the lastest V4L/DVB tree and
> pushed them to
> http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
> omap3isp-yuv. Could you please try them, and see if they're usable with your
> sensor ?

I just tried this kernel with my board.  The media control infrastructure
comes up and all of the devices are created, but I can't access them.

 From the bootup log:
   Linux media interface: v0.10
   Linux video capture interface: v2.00

When I try to access the devices:
   root@cobra3530p73:~# media-ctl -p
   Opening media device /dev/media0
   media_open_debug: Can't open media device /dev/media0
   Failed to open /dev/media0

The devices look OK to me:
   root@cobra3530p73:~# ls -l /dev/v*  /dev/med*
   crw------- 1 root root 252, 0 Nov  8 10:44 /dev/media0
   crw-rw---- 1 root video 81,   7 Nov  8 10:44 /dev/v4l-subdev0
   crw-rw---- 1 root video 81,   8 Nov  8 10:44 /dev/v4l-subdev1
   crw-rw---- 1 root video 81,   9 Nov  8 10:44 /dev/v4l-subdev2
   crw-rw---- 1 root video 81,  10 Nov  8 10:44 /dev/v4l-subdev3
   crw-rw---- 1 root video 81,  11 Nov  8 10:44 /dev/v4l-subdev4
   crw-rw---- 1 root video 81,  12 Nov  8 10:44 /dev/v4l-subdev5
   crw-rw---- 1 root video 81,  13 Nov  8 10:44 /dev/v4l-subdev6
   crw-rw---- 1 root video 81,  14 Nov  8 10:44 /dev/v4l-subdev7
   crw-rw---- 1 root video 81,  15 Nov  8 10:44 /dev/v4l-subdev8
   crw-rw---- 1 root tty    7,   0 Nov  8 10:44 /dev/vcs
   crw-rw---- 1 root tty    7,   1 Nov  8 10:44 /dev/vcs1
   crw-rw---- 1 root tty    7, 128 Nov  8 10:44 /dev/vcsa
   crw-rw---- 1 root tty    7, 129 Nov  8 10:44 /dev/vcsa1
   crw-rw---- 1 root video 81,   0 Nov  8 10:44 /dev/video0
   crw-rw---- 1 root video 81,   1 Nov  8 10:44 /dev/video1
   crw-rw---- 1 root video 81,   2 Nov  8 10:44 /dev/video2
   crw-rw---- 1 root video 81,   3 Nov  8 10:44 /dev/video3
   crw-rw---- 1 root video 81,   4 Nov  8 10:44 /dev/video4
   crw-rw---- 1 root video 81,   5 Nov  8 10:44 /dev/video5
   crw-rw---- 1 root video 81,   6 Nov  8 10:44 /dev/video6

Ideas?

Thanks

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

  reply	other threads:[~2012-01-19 12:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EBE38CF866F2F94F95FA9A8CB3EF2284069CAE@singex1.aptina.com>
2012-01-17 15:33 ` [PATCH] Adding YUV input support for OMAP3ISP driver Laurent Pinchart
2012-01-19 12:41   ` Gary Thomas [this message]
2012-01-19 12:50     ` Laurent Pinchart
2012-01-19 13:13       ` Gary Thomas
2012-01-19 13:28         ` Laurent Pinchart
2012-01-19 13:35           ` Gary Thomas
2012-01-19 13:52             ` Gary Thomas
2012-01-19 14:17               ` Enrico
2012-01-20 12:19                 ` Laurent Pinchart
2012-01-30 17:30                   ` Gary Thomas
2012-02-04 11:48                     ` Gary Thomas
2012-02-04 15:26                       ` Enrico
2012-03-08 15:04                         ` Enrico
2012-01-19 14:11             ` Javier Martinez Canillas
2012-01-19 14:36               ` Gary Thomas
2012-01-19 16:12                 ` Javier Martinez Canillas
2012-01-19 17:08                 ` Gary Thomas
2012-01-19 17:22                   ` Gary Thomas
2012-01-19 17:39                     ` Gary Thomas

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=4F180F95.7050003@mlbassoc.com \
    --to=gary@mlbassoc.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 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.