All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@linuxtv.org>
To: Salvatore Sanfilippo <antirez@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: v4l device in userspace
Date: Fri, 16 Jun 2006 10:18:52 -0400	[thread overview]
Message-ID: <4492BDCC.60207@linuxtv.org> (raw)
In-Reply-To: <c6114db60606160403g5e02becctbf2a67db7011ec9a@mail.gmail.com>

Salvatore Sanfilippo wrote:
> Hello, I'm trying to implement a v4l device driver
> for symbian based smart phones. In theory
> it is very simple:
>
> I've a little program running in the phone, capturing
> images from the camera and sending it to the
> linux box via bluetooth.
>
> In the linux box side, I've a deamon capturing this
> images (via a bluetooth SP channel), and....
> I've to pass the images to a fake v4l device
> driver that actually gets the images form userspace.
>
> Basically I've to pass by the kernel just for
> the interface, and not to do real kernel-side work
> (like to access to the some kind of hardware).
>
> So I've some questions ( thanks in advance
> for any reply).
>
> 1) What's the best way to pass relatively
> high-band data between the v4l fake driver
> and userspace? A char device will do the
> work? ioctl?
>
> 2) What about some way to handle ioctl
> directly from userspace? Given this support
> I may implement the whole code in userspace.
> And I guess there are a lot of other real world
> problems that can be handled in userspace
> given the ability to handle ioctl from there.
>
> If you think 2) is reasonable I may actually
> implement some simple form of generic
> char driver that just allows userspace
> programs to handle read/write/ioctl
> opreations, and then use this to fix
> my real issue.
>
> Thank you very much for the help,
> and sorry if there is something conceptually
> wrong in my questions.
>
> Regards,
> Salvatore
>
> P.S. please take me in CC as I'm not subscribed
> to the linux kernel mailing list.
>
I recommend resubmitting this question to a mailing list that actually 
focuses on this topic:

video4linux-list@redhat.com

However, I highly recommend that you subscribe before you post, as the 
redhat server adds a REPLY-TO header to the video4linux list emails, and 
has been known to drop cc's:

http://www.redhat.com/mailman/listinfo/video4linux-list

See you there!

-Michael Krufky

-- 
Michael Krufky



  parent reply	other threads:[~2006-06-16 14:19 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
2006-06-16 11:57   ` Salvatore Sanfilippo
2006-06-16 14:18 ` Michael Krufky [this message]
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=4492BDCC.60207@linuxtv.org \
    --to=mkrufky@linuxtv.org \
    --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 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.