From owner-freebsd-multimedia Wed Jun 20 13:42: 3 2001 Delivered-To: freebsd-multimedia@freebsd.org Received: from jupiter.linuxengine.net (jupiter.linuxengine.net [209.61.188.254]) by hub.freebsd.org (Postfix) with ESMTP id 925FB37B401 for ; Wed, 20 Jun 2001 13:41:59 -0700 (PDT) (envelope-from john@utzweb.net) Received: from jupiterweb.commercevault.com (jupiterweb.commercevault.com [209.61.179.16] (may be forged)) by jupiter.linuxengine.net (8.11.0/8.11.0) with ESMTP id f5KKgrR09871; Wed, 20 Jun 2001 15:42:53 -0500 Date: Wed, 20 Jun 2001 15:42:53 -0500 (CDT) From: John Utz X-X-Sender: To: Jamie Bowden Cc: Heiko Recktenwald , Kevin Walton , Tim Pozar , Subject: Re: BKTR Audio/Tuning problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org speaking *generally* FreeBSD looks for the unique id associated with the chip during the probe and if it isnt a magic number that it knows about, or chooses to look in the wrong place for some reason, then it never discovers the device properly. so, my usual hack in cases like this is to: 1. look at what the pc reports on boot up for the pci devices and jot down the string ie: "Foobar Technologies Frobish Device" 2. let the box boot to fbsd, su root and run pnpinfo andd look for the id associated with the string. 3. decide which device i am playing with and go to that code in the ksource. 4. a. hack that number into the detection code ( look for a big switch statement with weird numbers for each case ) b. put a kerror or kprintf or whatever it is as the first statement in the case so i can see if i actually hit the thing during boot. c. copy the implementation for *another* device in the same switch block in to the entry i just created. 5. rebuild the kernel, fixing compiler errors, and putting the kernel in the root with a weird name so that i remember to reboot with it when i feel like working on it. 6. reboot the box with my new weirdly named kernel 7. watch the bottmsg and wait to see if a. my string comes up b. the kernel panics because the chip is incompatible with the code that i just asked it to run when i cut and pasted in the other probe code :-) or c. it actually sort of half assed works :-) that's why it's called kernel hacking..... On Wed, 20 Jun 2001, Jamie Bowden wrote: > On Wed, 20 Jun 2001, Heiko Recktenwald wrote: > > :> Any more ideas? > : > :Are you shure you have radio on your card ? > : > :Here is my dmesg output, I think I dont have radio here, xmradio doesnt > :work: > : > :bktr0: mem 0xe2000000-0xe2000fff irq 9 at device 10.0 on pci0 > :iicbb0: on bti2c0 > :iicbus0: on iicbb0 master-only > :smbus0: on bti2c0 > :Miro TV, Temic PAL tuner. > : > :This is with FreeBSD 4.0-RELEASE #0: Mon Jun 18 15:38:54 CEST 2001. > : > :And I saw nothing for radio on Windows. The card is some MIROTV/PCI. > > I have a Studio PCTV Pro PCI with an FM tuner on it. FreeBSD sees it, but > calls it an unkown device. > > Jamie Bowden > > -- John L. Utz III john@utzweb.net Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message