On Friday 16 May 2008 18:50, Andy Walls wrote:
> On Tue, 2008-05-13 at 20:20 +0200, Hans Verkuil wrote:
> > On Tuesday 13 May 2008 13:50:18 [EMAIL PROTECTED] wrote:
> > > Hello everyone
> > >
> > > A few weeks ago, I bought a Video Encoder Card in Japan with the
> > > goal of using it there in a MythTV box.
> > >
> > > The card is branded "BUFFALO" and is called "PC-MV5L/PCI". The
> > > package says: "MPEG2 Hardware Encoder, TV tuner & VHS video
> > > capture board" (in Japanese).
> > >
> > > When booting my system, the kernel tells me that the card is
> > > unknown and that I should mail details to this mailing list
> > > (details are appended below). [Loading the firmware seems to be
> > > ok, though.]
> > >
> > > I compiled the latest kernel 2.6.25.3 from kernel.org to make
> > > sure I am not missing any important recent additions.
> > >
> > > The main chips on the PCI board are labeled:
> > > XCEIVE XC2028ACQ
> > > CONEXANT CX25843-24Z
> > > CONEXANT CX23416-22 MPEG II A/V ENCODER
> > > hynix 625A (memory?)
> > >
> > > As far as I can see in drivers/media/video/ivtv/ivtv-cards.c
> > > there might be a chance of getting this to run, since both the
> > > tuner (XC2028) and the MPEG2 Encoder (CX23416) seem to be
> > > supported by IVTV for other cards.
> > >
> > > Unfortunately, I have no clue how to come up with a new entry for
> > > ivtv-cards.c to recognize my device. I can provide more details
> > > about all the logic chips on the board, contents of the Windows
> > > driver cd, photographs of the board, or anything else. Just let
> > > me know.
> > >
> > > If anyone is able to help, I'd appreciate it very much!
> >
> > OK, a new card. There we go:
> >
> > 1) Get the new buffalo tree here:
> > http://linuxtv.org/hg/~hverkuil/buffalo/archive/tip.tar.bz2
> >
> > 2) make, make install, and run modprobe ivtv.
> >
> > 3) The card should be autodetected, now see if it works. Start with
> > the composite input (select using v4l2-ctl -i2).
> >
> > 4) If it does not work, then edit ivtv-cards.c: search for the
> > ivtv_card_buffalo struct, check out the line:
> >
> > { IVTV_CARD_INPUT_COMPOSITE1, 1, CX25840_COMPOSITE3 },
> >
> > in video_inputs. Replace CX25840_COMPOSITE3 with CX25840_COMPOSITE1
> > and try again. Then test with CX25840_COMPOSITE2, etc. etc. until
> > COMPOSITE8. One of these 8 possible inputs should work.
> >
> > Next try S-Video input (v4l2-ctl -i1): edit the line
> >
> > { IVTV_CARD_INPUT_SVIDEO1, 1, CX25840_SVIDEO3 },
> >
> > and replace SVIDEO3 with SVIDEO1-4 and see which one works. If none
> > of these works, or you get only black & white then make a note of
> > which input gives B&W and let me know. We can get color to work
> > later.
> >
> > 5) Tuner: first get the firmware. See the file
> > linux/Documentation/video4linux/extract_xc3028.pl for instructions.
> >
> > 6) Now modprobe ivtv. Then run rmmod ivtv and modprobe ivtv again.
> > If you get errors in the kernel log regarding the xceive tuner,
> > then you need to change the xceive_pin setting in the buffalo card
> > definition. It should be in the range 8-15. Try 10 first.
> >
> > 7) Congratulations, the tuner is now working. The final step is to
> > find the correct composite input for the tuner by editing the line:
> >
> > { IVTV_CARD_INPUT_VID_TUNER, 0, CX25840_COMPOSITE2 },
> >
> > Again, it can be any value from COMPOSITE1-8. For audio you may
> > have to change the line:
> >
> > { IVTV_CARD_INPUT_AUD_TUNER, CX25840_AUDIO5 },
> >
> > Possible values: AUDIO4-8.
> >
> > 8) Done!
> >
> > It's a bit annoying to go through all the combinations but it is
> > the only way to do it.
> >
> > BTW: check if your board has a WM8739 or MW8775 chip: that's a not
> > uncommon audio chip.
> >
> > Regards,
> >
> > Hans
>
> Hans,
>
> This seems like wiki material. I think it needs a forward section
> about building a starting card entry ivtv-cards.c and some tweaks to
> make it more generic, but it is a methodical process well worth
> documenting.
I was thinking the same thing. Either a wiki entry or a new
documentation file that's part of the v4l-dvb tree or put the
documentation in the ivtv-cards.c source itself as a big comment.
What's your opinion? I'm leaning towards putting it in the source itself
as that makes it easier to keep the documentation and the
implementation in sync.
> If you ever have time to write up an e-mail with a draft or sketch of
> the total process, making note of all the "oh by the way"s (which I
> suspect maybe only you know), I'll try to find time to clean it up
> and get it on the wiki.
I'll certainly ask you to review it.
> Since cx18 is "bone of ivtv's bone and flesh of ivtv's flesh",
How poetic! Much better than 'copy and paste'. :-)
> this
> process can be adapted to apply to getting new cards working for cx18
> as well.
Yes, it is very similar. Except for the very annoying memory chip ddr
settings, which is unique to the cx23418.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
