
poznick at conwaycorp
Jul 25, 2003, 8:49 PM
Post #2 of 17
(2272 views)
Permalink
|
Thus spake Tom Howard: > According to ivtv, the Freestyle should be compatible with its drivers > just as the PVR ?50's are. Considering you can get a freestyle for ~$90 > on newegg or other sites, Im thinking of making it my second tuner. Has > anyone tried it to verify that it does or doesnt work? If that's the card I believe it is, it should work. Someone had posted a link to http://www.z-buy.com/product.asp?item=VG-WINTVPP2 in the past couple of weeks. A co-worker bought one of those, thinking it was a PVR-250, and was too late to cancel the order. He went ahead and ordered a 250, but we decided to try out the other card anyway... I installed it this afternoon, and it's been working great so far. The only gotcha I've found so far was that I had to use test_ioctl -v input=3,output=1 to get the sound to work...I'd seen some mentions on the ivtv list of using the standard=0x21 option to msp3400 to get it to properly detect the audio standard, but that didn't seem to work for me. 00:09.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc.: Unknown device 4801 Flags: bus master, medium devsel, latency 32, IRQ 5 Memory at e0000000 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 Linux video capture interface: v1.00 ivtv: Found an unknown chip, treating it like an iTVC15 i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 0). i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 1). i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 2). i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 3). i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 4). i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 5). i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 6). i2c-core.o: client [EEPROM chip] registered to adapter [ivtv i2c driver #0](pos. 7). i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 2. ivtv: Encoder revision: 0x02030207 ivtv: Decoder revision: 0x02020001 ivtv: i2c client addr: 97 not found! ivtv: i2c client addr: 97 not found! ivtv: i2c client addr: 64 not found! ivtv: Registered v4l2 device, minor 0 ivtv: Registered v4l2 device, minor 32 ivtv: Registered v4l2 device, minor 224 i2c-core.o: driver i2c TV tuner driver registered. tuner: chip found @ 0xc2 tuner(bttv): type forced to 2 (Philips NTSC (FI1236,FM1236 and compatibles)) [insmod] i2c-core.o: client [Philips NTSC (FI1236,FM1236 and] registered to adapter [ivtv i2c driver #0](pos. 8). i2c-core.o: driver saa7115 registered. saa7114.c: starting probe for adapter SMBus Via Pro adapter at 5000 (0x40002) saa7114.c: starting probe for adapter ISA main adapter (0x50000) saa7114.c: starting probe for adapter ivtv i2c driver #0 (0x10005) saa7114.c: detecting saa7114 client on address 0x42 saa7115.c: writing init values status: (1E) 0x89, (1F) 0xb1 i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver #0](pos. 9). i2c-core.o: driver i2c msp3400 driver registered. msp34xx: init: chip=MSP3448W-A2, has NICAM support msp3410: daemon started i2c-core.o: client [MSP3448W-A2] registered to adapter [ivtv i2c driver #0](pos. 10). -- Nathan Poznick <poznick [at] conwaycorp> Ye shall know the truth, and the truth shall make you mad. - Aldous Huxley
|