linux-kernel - Re: [linux-dvb] [PATCH] Userspace tuner

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070918230058.GA17234@devserv.devel.redhat.com>
Date:	Tue, 18 Sep 2007 19:00:58 -0400
From:	Alan Cox <alan@...hat.com>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
Cc:	Jelle Foks <jelle@...s.8m.com>,
	"video4linux-list@...hat.com" <video4linux-list@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...hat.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-dvb@...uxtv.org" <linux-dvb@...uxtv.org>
Subject: Re: [linux-dvb] [PATCH] Userspace tuner

On Tue, Sep 18, 2007 at 07:56:05PM -0300, Mauro Carvalho Chehab wrote:
> proprietary format. This way, an userspace app may use the userspace
> library as a "fallback method" for unknown FOURCC formats. The result
> will be probably far away from an optimal result on some cases (since it
> probably mean double buffering), but this will at least allow userspace
> apps to work. As performance become an issue, the userspace app
> developer may use the GPL code at userspace API as a reference to write
> a proper optimized format driver for its apps.

You can dynamically load libraries based on constructed path names which
means you can write a simple library for media conversions which in turn
will try and open libv4l-format-ABCD.so for any format it doesn't know - and
thus is extensible

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/