From owner-freebsd-multimedia@FreeBSD.ORG Fri Jan 9 10:38:55 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAA9216A4CE for ; Fri, 9 Jan 2004 10:38:55 -0800 (PST) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF54243D45 for ; Fri, 9 Jan 2004 10:38:53 -0800 (PST) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp3.sentex.ca (8.12.10/8.12.10) with ESMTP id i09IcoU7028848 for ; Fri, 9 Jan 2004 13:38:50 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id i09IcpXw098746 for ; Fri, 9 Jan 2004 13:38:51 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.0.1.1.0.20040109132552.0771cea8@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Fri, 09 Jan 2004 13:37:57 -0500 To: freebsd-multimedia@freebsd.org From: Mike Tancsa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Subject: WinPVR 350 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2004 18:38:55 -0000 Encouraged by http://docs.freebsd.org/cgi/mid.cgi?200312050618.hB56IYi00447 I picked up a PVR 350 to use on my home firewall. The ability to schedule TV recordings via cron was just too tempting! However, much to my disappointment, it looks like the underlying chipset has changed enough not to work with the driver as posted. When loading the modules, I see Jan 9 10:19:09 cage /kernel: cxm0: mem 0xd8000000-0xdbffffff irq 12 at device 1.0 on pci1 Jan 9 10:19:09 cage /kernel: cxm_iic0: on cxm0 Jan 9 10:19:09 cage /kernel: iicbb0: on cxm_iic0 Jan 9 10:19:09 cage /kernel: iicbus0: on iicbb0 master-only Jan 9 10:19:09 cage /kernel: iicsmb0: on iicbus0 Jan 9 10:19:09 cage /kernel: smbus1: on iicsmb0 Jan 9 10:19:09 cage /kernel: smb1: on smbus1 Jan 9 10:19:09 cage /kernel: cxm0: unknown tuner code 0xf9 Jan 9 10:19:09 cage /kernel: cxm0: could not initialize tuner Jan 9 10:19:09 cage /kernel: device_probe_and_attach: cxm0 attach returned 6 Patching the code to max the tuner ID of 0xf9 match the listed tuners in the case statement does not work either. e.g. if I force it to one of the ones listed, it still barfs on the audio portion. If I force that as well to continue on, the unit does not initialize cxm0: Philips FM1246 tuner cxm0: SAA7115 rev 1 video decoder cxm0: unknown audio decoder MSP3448W-A2 -- continuing anyways cxm0: MSP3448W-A2 audio decoder cxm0: IR Remote cxm0: could not initialize hardware device_probe_and_attach: cxm0 attach returned 6 Has anyone had any luck with these newer models ? I had a look at the linux ivtv stuff and it seemed to treat the DSP the same as the MSP34xx series. But as for the video tuner, it made reference to a saa7127 which I wonder if this is one. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike