Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]tlug: bttv compatibility question
- To: tlug@example.com
- Subject: tlug: bttv compatibility question
- From: Marcus Metzler <mocm@example.com>
- Date: Fri, 26 Jun 1998 08:27:13 +0900 (JST)
- CC: rjkm@example.com
- Content-Type: text/plain; charset=ISO-2022-JP
- In-Reply-To: <13714.41022.521844.974661@example.com>
- References: <13714.41022.521844.974661@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
Kei Furuuchi writes: > Hi, > > I recently bought a Hauppauge Win/TV in hope that I can use it with > linux and bttv driver. But, I found that it uses new chip which > differs from bt848 description. > Namely, > >> > >> # cat /proc/pci > >> PCI devices found: > >> Bus 0, device 9, function 1: > >> Multimedia controller: Brooktree Unknown device (rev 2). > >> Vendor id=109e. Device id=878. > >> Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=64. Min Gnt=4.Max Lat=255. > >> Prefetchable 32 bit memory at 0xe4001000. > >> Bus 0, device 9, function 0: > >> Multimedia video controller: Brooktree Unknown device (rev 2). > >> Vendor id=109e. Device id=36e. > >> Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=64. Min Gnt=16.Max Lat=40. > >> Prefetchable 32 bit memory at 0xe4000000. > > also > >> # cat bttv/driver/bt848.h|grep DEVICE > >> #ifndef PCI_DEVICE_ID_BT848 > >> #define PCI_DEVICE_ID_BT848 0x350 > >> #ifndef PCI_DEVICE_ID_BT849 > >> #define PCI_DEVICE_ID_BT849 0x351 > > Also > >> # cat linux/include/linux/pci.h|grep BROOK > >> #define PCI_VENDOR_ID_BROOKTREE 0x109e > >> #define PCI_DEVICE_ID_BROOKTREE_848 0x0350 > > So it is new chip not defined by both linux and bttv. > And my questions are: > What is the prospect of supporting new chip? > What is the differece between SunVideo and bttv? > I haven`t heard about the SunVideo yet. We know that Haupauge is using a newer brooktree chip. There have already some questions about the compatibility. My brother wrote me that he thinks it should work if the driver is changed to recognize the new chip. He has told those who asked to try it, but he hasn`t got an answer yet. I will send this to him and ask him to tell me how to change the driver, so that you can try it if you want. Marcus ---------------------------------------------------------------------------- Dr. Marcus Metzler Department of Physics | $B")(B $B#2#7#4!<#8#5#1#0(B Toho University | $B@example.com)A%66;T;0;3#2!<#2!<#1(B Miyama 2-2-1, Funabashi, | $BElK.Bg3X(B $BM}3XIt(B $BJ*M}(B Chiba 274-8510 | Japan | e-mail : mocm@example.com ---------------------------------------------------------------------------- -------------------------------------------------------------- Next Nomikai: 17 July, 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Meeting: 8 August, Tokyo Station Yaesu central gate 12:30 featuring Linux on multiple platforms: i386, Sparc, PA-Risc, Amiga, SGI, Alpha, PalmPilot, ... -------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- tlug: bttv compatibility question
- From: Kei Furuuchi <kfur@example.com>
- References:
- tlug: bttv compatibility question
- From: Kei Furuuchi <kfur@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: GIMP against the rest(was Re: GUIs: Motif or ...? (was Re: tlug: Fw: Could Linux Kill NT?))
- Next by Date: Re: tlug: Success of Windows
- Prev by thread: tlug: bttv compatibility question
- Next by thread: tlug: bttv compatibility question
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links