From: Gergely Nagy <algernon@bonehunter.rulez.org>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Gergely Nagy <algernon@bonehunter.rulez.org>,
Luc Saillard <luc@saillard.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.9-ac3
Date: Fri, 22 Oct 2004 16:15:51 +0200 [thread overview]
Message-ID: <1098454551.15841.20.camel@melkor> (raw)
In-Reply-To: <1098448494.31003.37.camel@gonzales>
On Fri, 2004-10-22 at 14:34 +0200, Xavier Bestel wrote:
> Luc Saillard <luc@saillard.org> wrote:
> > On Fri, Oct 22, 2004 at 10:13:35AM +0200, Luca Risolia wrote:
> > > > o Restore PWC driver (Luc Saillard)
> > >
> > > This driver does decompression in kernel space, which is not
> > > allowed. That part has to be removed from the driver before
> > > asking for the inclusion in the mainline kernel.
> >
> > I know this problem, but without a user API like ALSA, each driver need to
> > implement the decompression module. When the driver will support v4l2, we can
> > return the compressed stream to the user land. I want a v4l3, which is
> > designed as ALSA does for soundcard, with a API for userland and kernelland.
>
> Why not use gstreamer as a userland API ? You deliver compressed video
> through v4l2, then write a decompression plugin specific to your
> chipset.
gstreamer might work for your average desktop application, and a
gstreamer plugin for this might be very handy indeed. However, there are
setups where gstreamer is just too bloated, and there's no way I could
squeeze it on the box's filesystem (think in the 8-16Mb range for
available space).
A small decoding library and a gstreamer plugin on top of that would be
the best solution, I think.
However, until there's such a thing, Luc's driver works fine for me and
my employer.
(Also, keep in mind that PWC thingies are pretty common in some circles,
and owners of these devices would like to see a working driver now.
Instead of a perfect one a year from now. Therefore, the driver staging
in the -ac tree is a very good thing, imho.)
--
Gergely Nagy
next prev parent reply other threads:[~2004-10-22 14:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 8:13 Linux 2.6.9-ac3 Luca Risolia
2004-10-22 9:21 ` Luc Saillard
2004-10-22 12:30 ` Luca Risolia
2004-10-22 12:34 ` Xavier Bestel
2004-10-22 13:33 ` Luc Saillard
2004-10-22 14:22 ` Ronald S. Bultje
2004-10-22 14:38 ` David Weinehall
2004-10-22 14:15 ` Gergely Nagy [this message]
2004-10-22 13:16 ` Luc Saillard
2004-10-22 14:07 ` Luca Risolia
2004-10-22 14:10 ` Gerd Knorr
2004-10-22 15:51 ` Alan Cox
2004-10-22 18:14 ` Gerd Knorr
2004-10-23 13:41 ` Luca Risolia
2004-10-22 11:09 ` Alan Cox
2004-10-22 13:00 ` Luca Risolia
2004-10-22 15:49 ` Alan Cox
2004-10-23 14:54 ` Bill Davidsen
2004-10-23 17:36 ` Luca Risolia
2004-10-25 22:22 ` Bill Davidsen
2004-10-26 5:29 ` Luc Saillard
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 23:08 Alan Cox
2004-10-22 0:59 ` Mark Lord
2004-10-22 1:18 ` Con Kolivas
2004-10-22 6:36 ` Jens Axboe
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=1098454551.15841.20.camel@melkor \
--to=algernon@bonehunter.rulez.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc@saillard.org \
--cc=xavier.bestel@free.fr \
/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