Return-path: Received: from brigitte.telenet-ops.be ([195.130.137.66]:52650 "EHLO brigitte.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751448AbZEVHFX (ORCPT ); Fri, 22 May 2009 03:05:23 -0400 Message-ID: <4A164D82.3050405@bsc-bvba.be> Date: Fri, 22 May 2009 09:00:18 +0200 From: Luc Brosens Reply-To: dvb2@bsc-bvba.be MIME-Version: 1.0 To: linux-media@vger.kernel.org CC: linux-dvb@linuxtv.org, tarik.chougua@yahoo.fr Subject: Re: [linux-dvb] Hauppauge WinTV-CI References: <965444.24352.qm@web26902.mail.ukl.yahoo.com> <20090515231650.56d6c4f4@bk.ru> In-Reply-To: <20090515231650.56d6c4f4@bk.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Goga777 wrote: >> Is Wintv-CI, the Common Interface from Hauppauge, working on linux now ? > > > not > > Goga > > _______________________________________________ I have been struggling for ages with this device, trying get the firmware to load. The program I wrote to extract the firmware from the driver now outputs the Intel Hex format too, used by fxload. No luck : the A3 part does not get loaded, not even using fxloads' A3-loader Details and downloads of code, logs etc at http://www.bsc-bvba.be/linux/dvb I could use some help, like : > traces of the firmware being loaded on XP/Vista (I am using USBspy myself), preferably using a hardware protocol analyser > recommendations for an affordable hardware USB2 protocol analyser (I'd try to compare the XP-log with the non-working Linux log) > suggestions on how to proceed ... Luc