linux-kernel - Re: 2.6.27 gspca driver fails with Trust WB-1400T

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1223932867.21717.8.camel@odie.local>
Date:	Mon, 13 Oct 2008 23:21:07 +0200
From:	Simon Holm Thøgersen <odie@...aau.dk>
To:	patrizio.bassi@...il.com
Cc:	"Kernel," <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.27 gspca driver fails with Trust WB-1400T

man, 13 10 2008 kl. 22:19 +0200, skrev Patrizio Bassi:
> Hi
> 
> i have a Trust 1400T perfectly working on 2.6.26 using external module
> (media-video/gspcav1-20071224 is the gentoo version so it's that day
> snapshot.)
> 
> Upgrading to 2.6.27 kernel, using integrated kernel driver
> 
Does the following text explain it (imagine the text being at the front
page of [2])?

"Historically, there has been a number of different projects ([1], ...),
providing v4l drivers outside of the mainline Linux kernel. If you are
migrating from drivers by such projects, you might need to know a few
things. The drivers provided by this project do not do various color
conversion routines in the kernel, but in a userspace library that we
also provide [3].

This means that programs that use v4l and v4l2 must either be
 - able to do the necessary color conversion themselves,
 - link against our userspace library that provides these
   conversions, or
 - be loaded using an appropriately set LD_PRELOAD environment
   variable."

[1] http://mxhaard.free.fr/
[2] http://linuxtv.org/v4lwiki/index.php/Main_Page
[3] http://linuxtv.org/hg/~hgoede/v4l-dvb


Simon Holm Thøgersen

--
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/