From: Pavel Machek <pavel@ucw.cz>
To: Salvatore Sanfilippo <antirez@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: v4l device in userspace
Date: Mon, 19 Jun 2006 23:57:18 +0200 [thread overview]
Message-ID: <20060619215718.GA1648@openzaurus.ucw.cz> (raw)
In-Reply-To: <c6114db60606160403g5e02becctbf2a67db7011ec9a@mail.gmail.com>
Hi!
> I've a little program running in the phone, capturing
> images from the camera and sending it to the
> linux box via bluetooth.
Nice!
> 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.
You probably want to do something v4l specigic... but generic userspace driver
able to do read/write/ioctl would be very nice. Lots of devices these days are on usb, and that can be done from userspace, for example.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
prev parent reply other threads:[~2006-06-19 22:32 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
2006-06-19 21:57 ` Pavel Machek [this message]
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=20060619215718.GA1648@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--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