The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Marcus Metzler <mocm@mocm.de>
To: "Salvatore Sanfilippo" <antirez@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: v4l device in userspace
Date: Fri, 16 Jun 2006 13:46:38 +0200	[thread overview]
Message-ID: <17554.39454.563004.916138@mocm.de> (raw)
In-Reply-To: <c6114db60606160403g5e02becctbf2a67db7011ec9a@mail.gmail.com>

>>>>> "Salvatore" == Salvatore Sanfilippo <antirez@gmail.com> writes:

    Salvatore> Hello, I'm trying to implement a v4l device driver for
    Salvatore> symbian based smart phones. In theory it is very
    Salvatore> simple:

    Salvatore> I've a little program running in the phone, capturing
    Salvatore> images from the camera and sending it to the linux box
    Salvatore> via bluetooth.

    Salvatore> In the linux box side, I've a deamon capturing this
    Salvatore> images (via a bluetooth SP channel), and....  I've to
    Salvatore> pass the images to a fake v4l device driver that
    Salvatore> actually gets the images form userspace.

    Salvatore> Basically I've to pass by the kernel just for the
    Salvatore> interface, and not to do real kernel-side work (like to
    Salvatore> access to the some kind of hardware).

    Salvatore> So I've some questions ( thanks in advance for any
    Salvatore> reply).

    Salvatore> 1) What's the best way to pass relatively high-band
    Salvatore> data between the v4l fake driver and userspace? A char
    Salvatore> device will do the work? ioctl?

    Salvatore> 2) What about some way to handle ioctl directly from
    Salvatore> userspace? Given this support I may implement the whole
    Salvatore> code in userspace.  And I guess there are a lot of
    Salvatore> other real world problems that can be handled in
    Salvatore> userspace given the ability to handle ioctl from there.

    Salvatore> If you think 2) is reasonable I may actually implement
    Salvatore> some simple form of generic char driver that just
    Salvatore> allows userspace programs to handle read/write/ioctl
    Salvatore> opreations, and then use this to fix my real issue.

    Salvatore> Thank you very much for the help, and sorry if there is
    Salvatore> something conceptually wrong in my questions.

Sounds like you should take a look at the v4l loopback device
(http://www.lavrsen.dk/twiki/bin/view/Motion/VideoFourLinuxLoopbackDevice).
Otherwise it may be better to ask the question on the v4l mailing list
(https://listman.redhat.com/mailman/listinfo/video4linux-list).

Anyway, since you already capture the video, why do you have to pipe
it through a v4l device? 

Marcus

-- 
/--------------------------------------------------------------------\
| Dr. Marcus O.C. Metzler        |                                   |
| mocm@metzlerbros.de            | http://www.metzlerbros.de/        |
\--------------------------------------------------------------------/
 |>>>             Quis custodiet ipsos custodes                 <<<|

  reply	other threads:[~2006-06-16 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 11:03 v4l device in userspace Salvatore Sanfilippo
2006-06-16 11:46 ` Marcus Metzler [this message]
2006-06-16 11:57   ` Salvatore Sanfilippo
2006-06-16 14:18 ` Michael Krufky
2006-06-19 21:57 ` Pavel Machek

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=17554.39454.563004.916138@mocm.de \
    --to=mocm@mocm.de \
    --cc=antirez@gmail.com \
    --cc=linux-kernel@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