Date: Thu, 28 Jan 1999 11:04:04 +0100 From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> To: Roger Hardiman <roger@cs.strath.ac.uk> Cc: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>, freebsd-multimedia@FreeBSD.ORG Subject: Re: Video works, Audio not on my new Hauppauge WinTV Message-ID: <19990128110404.A24908@internal> In-Reply-To: <36B02D61.DDC8B7EE@cs.strath.ac.uk>; from Roger Hardiman on Thu, Jan 28, 1999 at 09:26:57AM %2B0000 References: <19990128071216.A22152@internal> <36B02D61.DDC8B7EE@cs.strath.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 28-Jan-1999 at 09:26:57 +0000, Roger Hardiman wrote: > Hauppauge problems and 2.2.8-STABLE > > Andre Albsmeier wrote: > > Any hints what I can try? Maybe Roger knows a solution... > > Yes, I know the solution to all your problems :-) > 1) Driver version. > The version of the bt848/bt878 driver in 2.2.8-STABLE is really really > old. It does not support bt878s at all. > So, I have ported the 3.0-RELEASE driver to 225/226/227/228/22-stable > This can be found at ftp://telepresence.dmem.strath.ac.uk/pub/bt848/228 > > The driver from 3.0-RELEASE (ported to 228) DOES NOT support > audio on the Hauppauge cards with MSP34xx stereo audio chips > here in Europe. > > So, I recently added support for the MSP34xx audio chip and placed > this in my Development Test Drivers (beta driver). > You see this with the debugging output "Detected a MSP3410D-B4" Yes, this is the driver I am using now (actually because it was the newest one). > > 2) DMESG. > Well, for device probing, the new driver picks out the IR Remote > Control and the MSP34xx chip. > Both drivers you tested report this > > "pci0:12:1: vendor=0x109e, device=0x0878, class=multimedia (misc) int a > irq 11 [no driver assigned]" > > It is the audio capture hardware in the bt878. we do not use it > in FreeBSD. The hardware was added by Brooktree (now called Rockwell) > to allow Video+Audio capture in one card without the need for a > sound card. Understood. And I thought this was the tuner... > > As for "Phillips FI 1215MK2", the driver does know which tuner > you have, but it prints the wrong string "PAL I" on your screen. > The PAL I string should really say PAL (or PAL/BG) As I said, this info came from a _Win95_ diagnostics output. Now, what can I do to hear something? If I understood you correctly, I have the tuner being probed but it is probed falsely... > > while downloading the files stated above from > > telepresence.dmem.strath.ac.uk: > This is strange. This is my ftp site, and I upload the files with > ftp. There should be no ^Ms. > > Are you downloading the files in Windows or in Unix. > If you are downloading them in Windows, the problem is that > they are Unix ASCII files. > DOS/Windows and Unix store the "end of line" marker differently > and each system reads the other's files but with ^M. In Unix, of course :-) But I live behind a firewall and I have just downloaded them from outside on a FreeBSD machine using fetch, and here all works as expected. So don't be alerted, it seems to be a problem/feature with the firewall here... Thanks in advance for your help, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990128110404.A24908>