On Monday 14 January 2008 22:11:45 George Galt wrote:
> Hans:
>
> Does this board use the same chips as the functionally equivalent
> HVR-1800? I'm left with only PCI-e slots and am hoping to use the
> HVR-1800 when ivtv can handle both the digital and analog signals.
The HVR-1800 uses a different chip, but I know work is in progress. See
the video4linux mailinglist.
Regards,
Hans
>
> Thanks,
>
> George
>
> On Jan 14, 2008 1:59 AM, Hans Verkuil <[EMAIL PROTECTED]> wrote:
> > On Monday 14 January 2008 04:45:54 Anthony Cipolone wrote:
> > > Someone posted this morning (I just joined the list, otherwise I
> > > would reply!) and I had nearly the exact same results:
> > >
> > > I'm running this on KnoppMyth R5F27, which uses the 2.6.18
> > > kernel. I had to patch as per here this post:
> > > http://www.gossamer-threads.com/lists/ivtv/devel/37190#37190 in
> > > order to get it to build.
> > >
> > > After "make" and "make install" and copying the firmware (from
> > > http://ivtvdriver.org/index.php/Cx18) I had to completely power
> > > down -- a soft reboot gave a bunch of errors eeprom and i2c
> > > errors. "make unload" gave some errors, probably due to MythTV
> > > running.
> > >
> > > >From dmesg | grep cx18:
> > >
> > > cx18: Start initialization, version 0.1.0
> > > cx18-0: Initializing card #0
> > > cx18-0: Autodetected Hauppauge card
> > > cx18-0: cx23418 revision 01010000 (B)
> > > tuner' 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
> > > cx18-0: Autodetected Hauppauge HVR-1600
> > > cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
> > > cx18-0: Disabled encoder IDX device
> > > cx18-0: Registered device video0 for encoder MPEG (2 MB)
> > > cx18-0: Registered device video16 for TS (2 MB)
> > > cx18-0: Registered device video32 for encoder YUV (2 MB)
> > > cx18-0: Registered device vbi0 for encoder VBI (1 MB)
> > > cx18-0: Registered device video24 for encoder PCM audio (1 MB)
> > > cx18-0: Initialized card #0: Hauppauge HVR-1600
> > > cx18: End initialization
> > > cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200
> > > bytes) cx18-0: loaded v4l-cx23418-cpu.fw firmware (174716 bytes)
> > > cx18-0: debug: 1 MiniMe Encoder Firmware 0.0.71.0 (Release
> > > 2006/12/29) cx18-0: FW version: 0.0.71.0 (Release 2006/12/29)
> > > cx18-0: Took ~20 mS for FW to start
> > > cx18-0: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
> > >
> > > After running either "cat /dev/video0 > test.mpg" this appears in
> > > dmesg:
> > >
> > > cx18-0: Unknown cmd 9b
> > > cx18-0: Unknown cmd 9f
> > > cx18-0: Unknown cmd a1
> > > cx18-0: Unknown cmd 9d
> >
> > This can be ignored. I still need to handle these commands, but
> > they are not important.
> >
> > > Much the same as posted earlier this morning. The only difference
> > > is in "lspci -v". I get:
> > >
> > > 02:0a.0 Multimedia video controller: Conexant Unknown device 5b7a
> > > Subsystem: Hauppauge computer works Inc. Unknown device
> > > 7444 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory
> > > at f4000000 (32-bit, non-prefetchable) [size=64M] Capabilities:
> > > [44] Vital Product Data
> > > Capabilities: [4c] Power Management version 2
> > >
> > > Showing "Unknown device 5b7a" instead of "Conexant CX23418
> > > Single-Chip MPEG-2".
> >
> > I think it is missing in the lspci database, not relevant to the
> > driver.
> >
> > > tveeprom in dmesg shows:
> > >
> > > tveeprom 1-0050: Hauppauge model 74041, rev C5B2, serial# 2883873
> > >
> > > Running "mplayer /dev/video0" shows video just fine (however,
> > > unrelated to this list, MythTV shows a black screen then backs
> > > out to the menu).
> > >
> > > I know there was some questions about the 74041s, but it seems to
> > > work okay here ... sorta.
> >
> > I think I've sorted the last init problems this weekend.
> >
> > > Thanks for all the work being done on this card! I received it
> > > as a gift and was going to return it since there's no stable
> > > drivers, but thought that helping to test it would probably help
> > > those stable drivers come out sooner. If there's any other
> > > information I can provide, let me know!
> >
> > The important bit here is that the card initializes properly. That
> > was blocking me from refining other parts of the driver. But I
> > think I cracked that this weekend.
> >
> > Regards,
> >
> > Hans
> >
> > _______________________________________________
> > ivtv-devel mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
