From owner-freebsd-multimedia@FreeBSD.ORG Sun Jun 11 20:43:50 2006 Return-Path: X-Original-To: freebsd-multimedia@freebsd.org 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 9672D16A59A for ; Sun, 11 Jun 2006 20:43:50 +0000 (UTC) (envelope-from cyberbotx@cyberbotx.com) Received: from samus.cyberbotx.com (cyberbotx.com [70.88.125.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3142F43D45 for ; Sun, 11 Jun 2006 20:43:50 +0000 (GMT) (envelope-from cyberbotx@cyberbotx.com) Received: from localhost (localhost [127.0.0.1]) by samus.cyberbotx.com (Postfix) with ESMTP id A4CAFC6CE for ; Sun, 11 Jun 2006 16:46:45 -0400 (EDT) X-Virus-Scanned: amavisd-new at cyberbotx.com Received: from samus.cyberbotx.com ([127.0.0.1]) by localhost (samus.cyberbotx.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJcqc8JKrM7C for ; Sun, 11 Jun 2006 16:46:20 -0400 (EDT) Received: from metroid (c-68-61-58-20.hsd1.mi.comcast.net [68.61.58.20]) by samus.cyberbotx.com (Postfix) with SMTP id 27231C0E0 for ; Sun, 11 Jun 2006 16:46:20 -0400 (EDT) Message-ID: <0b3d01c68d97$af0de7a0$fe02a8c0@metroid> From: "Naram Qashat" To: References: <200606111157.k5BBvdog054178@amd64.ott.parse.com> Date: Sun, 11 Jun 2006 16:43:23 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: Re: bktr problems X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jun 2006 20:43:50 -0000 That's a little helpful. How do I determine what values to use? And what's the easiest way to test the changes? Right now, I've got the bktr module compiled directly into the kernel. But last time I tried to not compile it into the kernel and load it as a module seperately, it failed to load, I think it might've been because of the other device lines that the bktr page in the FreeBSD handbook says are needed. Naram Qashat ----- Original Message ----- From: "Robert Krten" To: Sent: Sunday, June 11, 2006 07:57 AM Subject: Re: bktr problems > Danny Pansters sez... > > > > On Sunday 11 June 2006 10:23, Naram Qashat wrote: > > > I've been having problems with my bktr-based TV Tuner card. It's a > > > Hauppauge WinTV GO-Plus, and a pretty recent model too. Next is the > > > messages for the driver upon bootup: > > > > > > bktr0: mem 0xdc000000-0xdc000fff irq 11 at device 9.0 on > > > pci1 > > > bktr0: [GIANT-LOCKED] > > > bktr0: Hauppauge Model 29440 @ % > > > bktr0: Warning - Unknown Hauppauge Tuner 0xd5 > > ^^^^^^^^^^^^^^^^^^^^^^^^ > > > > /usr/src/sys/dev/bktr/bktr_card.c has some interesting comments about (some?) > > bt878 based cards that have an EEPROM. In short: they've been broken by the > > time MT2032 tuner support was added, and they're still broken. I've had > > similar problems with an (old) WinCast TV card; it stopped working somewhere > > around FreeBSD-5.3 or so, also because tuner detection fails and it can't be > > bullied into using the correct one with sysctl. I tried to raise the issue > > several times but never got a response. > > I had a similar problem, I had to add a tuner card. > > Mine was a "type 0x79". Your type "0xd5" may or may not be the same type of > tuner chip... > > Here's what I did to add my 0x79 type: > > And the line you need to add (in bktr_card.c) is: > > switch (tuner_code) { > ... > ... > ... > case 0x79: > select_tuner( bktr, PHILIPS_TDA6503_NTSC ); > goto checkDBX; > } > > And you need to add the PHILIPS_TDA6503_NTSC info in: > > bktr_tuner.h:#define PHILIPS_TDA6503_NTSC 15 > > (Or whatever number is next in the table, in case I have older source) > > And the following in bktr_tuner.c: > > /* PHILIPS_TDA6503_NTSC */ > { "Philips TDA6503 NTSC", /* the 'name' */ > TTYPE_NTSC, /* input type */ > { TSA552x_SCONTROL, /* control byte for Tuner PLL */ > TSA552x_SCONTROL, > TSA552x_SCONTROL, > 0x00 }, > { 0x00, 0x00 }, /* band-switch crosspoints */ > { 0x01, 0x02, 0x08, 0x00 } } /* the band-switch values */ > > You need to match up the #define index with the position in the table > above, I think. > > If your chip is different than mine, you'll need to figure out different > parameters for the bktr_tuner.c module hacks... > > Cheers, > -RK > > -- > Robert Krten, PARSE Software Devices > Realtime Systems Architecture, Consulting, Books and Training at www.parse.com > Looking for Digital Equipment Corp. PDP-1 through PDP-15 minicomputers! > _______________________________________________ > freebsd-multimedia@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia > To unsubscribe, send any mail to "freebsd-multimedia-unsubscribe@freebsd.org"