Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754485AbYJONKL (ORCPT ); Wed, 15 Oct 2008 09:10:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752888AbYJONJ6 (ORCPT ); Wed, 15 Oct 2008 09:09:58 -0400 Received: from wr-out-0506.google.com ([64.233.184.226]:10058 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752855AbYJONJ5 (ORCPT ); Wed, 15 Oct 2008 09:09:57 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Lk9MjdyVoUZjorqnrLHjEou1g7WB5nvjG4uE+WrDBkJDybG7K958a7C3AKN6L1xeEH wNQI4dtwcKvDMpc9zFEjfREi+/ob6MN/D5/7idwCWpzZJ8Lowk1b6Cb8uE42/LAywmW+ v6jATKiSh7MBxhbvq+FvkFKTTpi4cHxOedQXs= Message-ID: <742b1fb30810150609u3fb8d877meb8c9182d065c6c4@mail.gmail.com> Date: Wed, 15 Oct 2008 15:09:55 +0200 From: "Patrizio Bassi" To: "=?UTF-8?Q?Simon_Holm_Th=C3=B8gersen?=" Subject: Re: 2.6.27 gspca driver fails with Trust WB-1400T Cc: "Kernel," In-Reply-To: <742b1fb30810140021h565520c3oa102005a539d6a1f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline References: <48F3AD5A.2080504@gmail.com> <1223932867.21717.8.camel@odie.local> <742b1fb30810140021h565520c3oa102005a539d6a1f@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by alpha id m9FDAFdq031548 Content-Length: 1966 Lines: 5 2008/10/14 Patrizio Bassi >> 2008/10/13 Simon Holm Thøgersen > >> > 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> >>> ok, it sounds i need to read some wikis...i'll come back to you when> i'm done with the result> Hi Simon, with the v4llib it looks much better, even if colors are not real as before.I think i need to tune it a little bit. In the driver homepage it seems they suggest to continue using the olddriver with kernelspace decode for desktop or fast machines, butunfortunatly it doesn't even compile with 2.6.27. --Patrizio Bassiwww.patriziobassi.it????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?