Mailing List Archive: ivtv: devel

[UNKNOWN IVTV CARD] [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan

Index | Next | Previous | View Threaded

me146983 at oku

May 13, 2008, 4:50 AM

Post #1 of 13 (4744 views)
Permalink

[UNKNOWN IVTV CARD] [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan

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!

Thanks,
Peter

==============================================================
relevant sections from "dmesg"
==============================================================
[ 0.000000] Linux version 2.6.25.3-pkb (root [at] tereb) (gcc version
4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon May 12 18:53:18 JST 2008
...skip...
[ 34.535451] agpgart: Detected VIA CLE266 chipset
[ 34.536713] agpgart: AGP aperture is 4M @ 0xea000000
[ 34.812244] Linux video capture interface: v2.00
[ 35.730306] ivtv: Start initialization, version 1.2.0
[ 35.731953] ivtv0: Initializing card #0
[ 35.732032] ivtv0: Unknown card: vendor/device: 4444/0016
[ 35.732099] ivtv0: subsystem vendor/device: 1154/052b
[ 35.732168] ivtv0: cx23416 based
[ 35.732228] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
[ 35.732299] ivtv0: Please mail the vendor/device and subsystem
vendor/device IDs and what kind of
[ 35.732388] ivtv0: card you have to the ivtv-devel mailinglist
(www.ivtvdriver.org)
[ 35.732469] ivtv0: Prefix your subject line with [UNKNOWN IVTV CARD].
[ 35.802255] ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKB] -> GSI
10 (level, low) -> IRQ 10
[ 35.802433] ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
[ 36.787796] tveeprom 1-0050: Encountered bad packet header [ff].
Corrupt or not a Hauppauge eeprom.
[ 36.787899] ivtv0: Invalid EEPROM
[ 37.986916] input: Power Button (FF) as /class/input/input4
[ 38.014101] ACPI: Power Button (FF) [PWRF]
[ 38.021253] input: Power Button (CM) as /class/input/input5
[ 38.054021] ACPI: Power Button (CM) [PWRB]
[ 43.399074] cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
[ 43.409132] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
[ 43.412483] wm8775 1-001b: I2C: cannot write 000 to register R23
[ 43.415824] wm8775 1-001b: I2C: cannot write 000 to register R7
[ 43.419118] wm8775 1-001b: I2C: cannot write 021 to register R11
[ 43.422431] wm8775 1-001b: I2C: cannot write 102 to register R12
[ 43.425741] wm8775 1-001b: I2C: cannot write 000 to register R13
[ 43.429135] wm8775 1-001b: I2C: cannot write 1d4 to register R14
[ 43.432443] wm8775 1-001b: I2C: cannot write 1d4 to register R15
[ 43.455893] wm8775 1-001b: I2C: cannot write 1bf to register R16
[ 43.506726] wm8775 1-001b: I2C: cannot write 185 to register R17
[ 43.572995] wm8775 1-001b: I2C: cannot write 0a2 to register R18
[ 43.630442] wm8775 1-001b: I2C: cannot write 005 to register R19
[ 43.688818] wm8775 1-001b: I2C: cannot write 07a to register R20
[ 43.798126] wm8775 1-001b: I2C: cannot write 102 to register R21
[ 43.834579] ivtv0: Registered device video0 for encoder MPG (4096 kB)
[ 43.847960] ivtv0: Registered device video32 for encoder YUV (2048 kB)
[ 43.854508] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
[ 43.861131] ivtv0: Registered device video24 for encoder PCM (320 kB)
[ 43.875737] ivtv0: Registered device radio0 for encoder radio
[ 43.875819] ivtv0: Initialized card #0: Hauppauge WinTV PVR-150
[ 43.882291] ivtv: End initialization
[ 44.183080] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI
11 (level, low) -> IRQ 11
[ 44.328232] fb0: VIA VT8623 on 0000:01:00.0, 16 MB RAM
[ 45.301070] parport_pc 00:0b: reported by Plug and Play ACPI
[ 45.301180] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
...skip...
[ 73.898006] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[ 73.898037] apm: overridden by ACPI.
[ 74.505237] ppdev: user-space parallel port driver
[ 75.544316] Clocksource tsc unstable (delta = -69390330 ns)
[ 78.972664] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[ 79.169899] ivtv0: Encoder revision: 0x02060039
[ 82.973240] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[ 83.144925] wm8775 1-001b: I2C: cannot write 0c0 to register R21
[ 83.150816] wm8775 1-001b: I2C: cannot write 1d4 to register R14
[ 83.156603] wm8775 1-001b: I2C: cannot write 1d4 to register R15
[ 83.162395] wm8775 1-001b: I2C: cannot write 102 to register R21
[ 83.224920] wm8775 1-001b: I2C: cannot write 0c0 to register R21
[ 83.230734] wm8775 1-001b: I2C: cannot write 1d4 to register R14
[ 83.236512] wm8775 1-001b: I2C: cannot write 1d4 to register R15
[ 83.242318] wm8775 1-001b: I2C: cannot write 102 to register R21
[ 83.271840] wm8775 1-001b: I2C: cannot write 0c0 to register R21
[ 83.277625] wm8775 1-001b: I2C: cannot write 1d4 to register R14
[ 83.283436] wm8775 1-001b: I2C: cannot write 1d4 to register R15
[ 83.289213] wm8775 1-001b: I2C: cannot write 108 to register R21
[ 83.366955] wm8775 1-001b: I2C: cannot write 0c0 to register R21
[ 83.372946] wm8775 1-001b: I2C: cannot write 1d4 to register R14
[ 83.378749] wm8775 1-001b: I2C: cannot write 1d4 to register R15
[ 83.384511] wm8775 1-001b: I2C: cannot write 102 to register R21
[ 84.557735] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 84.627866] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
...skip...

==============================================================
# lspci -vvv
==============================================================
...skip...
00:14.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)
Subsystem: Melco Inc Unknown device 052b
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
...skip...

==============================================================
# lspci -vvv -nn
==============================================================
...skip...
00:14.0 Multimedia video controller [0400]: Internext Compression Inc
iTVC16 (CX23416) MPEG-2 Encoder [4444:0016] (rev 01)
Subsystem: Melco Inc Unknown device [1154:052b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
...skip...

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

sander.sweers at gmail

May 13, 2008, 6:59 AM

Post #2 of 13 (4625 views)
Permalink

Re: [UNKNOWN IVTV CARD] [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

On Tue, May 13, 2008 at 1:50 PM, <me146983 [at] oku> wrote:
<snip>
> 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).
>
<snip>
>
> 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.

You can try to override the tuner by adding a module option to ivtv.
Try loading it with tuner=71 and see if this makes it work. It might
need more work than that but this is the easiest.

Greets
Sander

> ==============================================================
> relevant sections from "dmesg"
> ==============================================================
> [ 0.000000] Linux version 2.6.25.3-pkb (root [at] tereb) (gcc version
> 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon May 12 18:53:18 JST 2008
> ...skip...
> [ 34.535451] agpgart: Detected VIA CLE266 chipset
> [ 34.536713] agpgart: AGP aperture is 4M @ 0xea000000
> [ 34.812244] Linux video capture interface: v2.00
> [ 35.730306] ivtv: Start initialization, version 1.2.0
> [ 35.731953] ivtv0: Initializing card #0
> [ 35.732032] ivtv0: Unknown card: vendor/device: 4444/0016
> [ 35.732099] ivtv0: subsystem vendor/device: 1154/052b
> [ 35.732168] ivtv0: cx23416 based
> [ 35.732228] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
> [ 35.732299] ivtv0: Please mail the vendor/device and subsystem
> vendor/device IDs and what kind of
> [ 35.732388] ivtv0: card you have to the ivtv-devel mailinglist
> (www.ivtvdriver.org)
> [ 35.732469] ivtv0: Prefix your subject line with [UNKNOWN IVTV CARD].
> [ 35.802255] ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKB] -> GSI
> 10 (level, low) -> IRQ 10
> [ 35.802433] ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> [ 36.787796] tveeprom 1-0050: Encountered bad packet header [ff].
> Corrupt or not a Hauppauge eeprom.
> [ 36.787899] ivtv0: Invalid EEPROM
> [ 37.986916] input: Power Button (FF) as /class/input/input4
> [ 38.014101] ACPI: Power Button (FF) [PWRF]
> [ 38.021253] input: Power Button (CM) as /class/input/input5
> [ 38.054021] ACPI: Power Button (CM) [PWRB]
> [ 43.399074] cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
> [ 43.409132] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> [ 43.412483] wm8775 1-001b: I2C: cannot write 000 to register R23
> [ 43.415824] wm8775 1-001b: I2C: cannot write 000 to register R7
> [ 43.419118] wm8775 1-001b: I2C: cannot write 021 to register R11
> [ 43.422431] wm8775 1-001b: I2C: cannot write 102 to register R12
> [ 43.425741] wm8775 1-001b: I2C: cannot write 000 to register R13
> [ 43.429135] wm8775 1-001b: I2C: cannot write 1d4 to register R14
> [ 43.432443] wm8775 1-001b: I2C: cannot write 1d4 to register R15
> [ 43.455893] wm8775 1-001b: I2C: cannot write 1bf to register R16
> [ 43.506726] wm8775 1-001b: I2C: cannot write 185 to register R17
> [ 43.572995] wm8775 1-001b: I2C: cannot write 0a2 to register R18
> [ 43.630442] wm8775 1-001b: I2C: cannot write 005 to register R19
> [ 43.688818] wm8775 1-001b: I2C: cannot write 07a to register R20
> [ 43.798126] wm8775 1-001b: I2C: cannot write 102 to register R21
> [ 43.834579] ivtv0: Registered device video0 for encoder MPG (4096 kB)
> [ 43.847960] ivtv0: Registered device video32 for encoder YUV (2048 kB)
> [ 43.854508] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> [ 43.861131] ivtv0: Registered device video24 for encoder PCM (320 kB)
> [ 43.875737] ivtv0: Registered device radio0 for encoder radio
> [ 43.875819] ivtv0: Initialized card #0: Hauppauge WinTV PVR-150
> [ 43.882291] ivtv: End initialization
> [ 44.183080] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI
> 11 (level, low) -> IRQ 11
> [ 44.328232] fb0: VIA VT8623 on 0000:01:00.0, 16 MB RAM
> [ 45.301070] parport_pc 00:0b: reported by Plug and Play ACPI
> [ 45.301180] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
> ...skip...
> [ 73.898006] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
> [ 73.898037] apm: overridden by ACPI.
> [ 74.505237] ppdev: user-space parallel port driver
> [ 75.544316] Clocksource tsc unstable (delta = -69390330 ns)
> [ 78.972664] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> [ 79.169899] ivtv0: Encoder revision: 0x02060039
> [ 82.973240] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> [ 83.144925] wm8775 1-001b: I2C: cannot write 0c0 to register R21
> [ 83.150816] wm8775 1-001b: I2C: cannot write 1d4 to register R14
> [ 83.156603] wm8775 1-001b: I2C: cannot write 1d4 to register R15
> [ 83.162395] wm8775 1-001b: I2C: cannot write 102 to register R21
> [ 83.224920] wm8775 1-001b: I2C: cannot write 0c0 to register R21
> [ 83.230734] wm8775 1-001b: I2C: cannot write 1d4 to register R14
> [ 83.236512] wm8775 1-001b: I2C: cannot write 1d4 to register R15
> [ 83.242318] wm8775 1-001b: I2C: cannot write 102 to register R21
> [ 83.271840] wm8775 1-001b: I2C: cannot write 0c0 to register R21
> [ 83.277625] wm8775 1-001b: I2C: cannot write 1d4 to register R14
> [ 83.283436] wm8775 1-001b: I2C: cannot write 1d4 to register R15
> [ 83.289213] wm8775 1-001b: I2C: cannot write 108 to register R21
> [ 83.366955] wm8775 1-001b: I2C: cannot write 0c0 to register R21
> [ 83.372946] wm8775 1-001b: I2C: cannot write 1d4 to register R14
> [ 83.378749] wm8775 1-001b: I2C: cannot write 1d4 to register R15
> [ 83.384511] wm8775 1-001b: I2C: cannot write 102 to register R21
> [ 84.557735] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 84.627866] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> ...skip...
>
>
> ==============================================================
> # lspci -vvv
> ==============================================================
> ...skip...
> 00:14.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Melco Inc Unknown device 052b
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 10
> Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> ...skip...
>
>
> ==============================================================
> # lspci -vvv -nn
> ==============================================================
> ...skip...
> 00:14.0 Multimedia video controller [0400]: Internext Compression Inc
> iTVC16 (CX23416) MPEG-2 Encoder [4444:0016] (rev 01)
> Subsystem: Melco Inc Unknown device [1154:052b]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 10
> Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> ...skip...
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

hverkuil at xs4all

May 13, 2008, 11:20 AM

Post #3 of 13 (4615 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

On Tuesday 13 May 2008 13:50:18 me146983 [at] oku 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

>
> Thanks,
> Peter
>
> ==============================================================
> relevant sections from "dmesg"
> ==============================================================
> [ 0.000000] Linux version 2.6.25.3-pkb (root [at] tereb) (gcc version
> 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon May 12 18:53:18 JST 2008
> ...skip...
> [ 34.535451] agpgart: Detected VIA CLE266 chipset
> [ 34.536713] agpgart: AGP aperture is 4M @ 0xea000000
> [ 34.812244] Linux video capture interface: v2.00
> [ 35.730306] ivtv: Start initialization, version 1.2.0
> [ 35.731953] ivtv0: Initializing card #0
> [ 35.732032] ivtv0: Unknown card: vendor/device: 4444/0016
> [ 35.732099] ivtv0: subsystem vendor/device:
> 1154/052b [ 35.732168] ivtv0: cx23416 based
> [ 35.732228] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
> [ 35.732299] ivtv0: Please mail the vendor/device and subsystem
> vendor/device IDs and what kind of
> [ 35.732388] ivtv0: card you have to the ivtv-devel mailinglist
> (www.ivtvdriver.org)
> [ 35.732469] ivtv0: Prefix your subject line with [UNKNOWN IVTV
> CARD]. [ 35.802255] ACPI: PCI Interrupt 0000:00:14.0[A] -> Link
> [LNKB] -> GSI 10 (level, low) -> IRQ 10
> [ 35.802433] ivtv0: Unreasonably low latency timer, setting to 64
> (was 32) [ 36.787796] tveeprom 1-0050: Encountered bad packet
> header [ff]. Corrupt or not a Hauppauge eeprom.
> [ 36.787899] ivtv0: Invalid EEPROM
> [ 37.986916] input: Power Button (FF) as /class/input/input4
> [ 38.014101] ACPI: Power Button (FF) [PWRF]
> [ 38.021253] input: Power Button (CM) as /class/input/input5
> [ 38.054021] ACPI: Power Button (CM) [PWRB]
> [ 43.399074] cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c
> driver #0) [ 43.409132] wm8775 1-001b: chip found @ 0x36 (ivtv i2c
> driver #0) [ 43.412483] wm8775 1-001b: I2C: cannot write 000 to
> register R23 [ 43.415824] wm8775 1-001b: I2C: cannot write 000 to
> register R7 [ 43.419118] wm8775 1-001b: I2C: cannot write 021 to
> register R11 [ 43.422431] wm8775 1-001b: I2C: cannot write 102 to
> register R12 [ 43.425741] wm8775 1-001b: I2C: cannot write 000 to
> register R13 [ 43.429135] wm8775 1-001b: I2C: cannot write 1d4 to
> register R14 [ 43.432443] wm8775 1-001b: I2C: cannot write 1d4 to
> register R15 [ 43.455893] wm8775 1-001b: I2C: cannot write 1bf to
> register R16 [ 43.506726] wm8775 1-001b: I2C: cannot write 185 to
> register R17 [ 43.572995] wm8775 1-001b: I2C: cannot write 0a2 to
> register R18 [ 43.630442] wm8775 1-001b: I2C: cannot write 005 to
> register R19 [ 43.688818] wm8775 1-001b: I2C: cannot write 07a to
> register R20 [ 43.798126] wm8775 1-001b: I2C: cannot write 102 to
> register R21 [ 43.834579] ivtv0: Registered device video0 for
> encoder MPG (4096 kB) [ 43.847960] ivtv0: Registered device video32
> for encoder YUV (2048 kB) [ 43.854508] ivtv0: Registered device
> vbi0 for encoder VBI (1024 kB) [ 43.861131] ivtv0: Registered
> device video24 for encoder PCM (320 kB) [ 43.875737] ivtv0:
> Registered device radio0 for encoder radio [ 43.875819] ivtv0:
> Initialized card #0: Hauppauge WinTV PVR-150 [ 43.882291] ivtv:
> End initialization
> [ 44.183080] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] ->
> GSI 11 (level, low) -> IRQ 11
> [ 44.328232] fb0: VIA VT8623 on 0000:01:00.0, 16 MB RAM
> [ 45.301070] parport_pc 00:0b: reported by Plug and Play ACPI
> [ 45.301180] parport0: PC-style at 0x378, irq 7
> [PCSPP,TRISTATE,EPP] ...skip...
> [ 73.898006] apm: BIOS version 1.2 Flags 0x07 (Driver version
> 1.16ac) [ 73.898037] apm: overridden by ACPI.
> [ 74.505237] ppdev: user-space parallel port driver
> [ 75.544316] Clocksource tsc unstable (delta = -69390330 ns)
> [ 78.972664] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836
> bytes) [ 79.169899] ivtv0: Encoder revision: 0x02060039
> [ 82.973240] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382
> bytes) [ 83.144925] wm8775 1-001b: I2C: cannot write 0c0 to
> register R21 [ 83.150816] wm8775 1-001b: I2C: cannot write 1d4 to
> register R14 [ 83.156603] wm8775 1-001b: I2C: cannot write 1d4 to
> register R15 [ 83.162395] wm8775 1-001b: I2C: cannot write 102 to
> register R21 [ 83.224920] wm8775 1-001b: I2C: cannot write 0c0 to
> register R21 [ 83.230734] wm8775 1-001b: I2C: cannot write 1d4 to
> register R14 [ 83.236512] wm8775 1-001b: I2C: cannot write 1d4 to
> register R15 [ 83.242318] wm8775 1-001b: I2C: cannot write 102 to
> register R21 [ 83.271840] wm8775 1-001b: I2C: cannot write 0c0 to
> register R21 [ 83.277625] wm8775 1-001b: I2C: cannot write 1d4 to
> register R14 [ 83.283436] wm8775 1-001b: I2C: cannot write 1d4 to
> register R15 [ 83.289213] wm8775 1-001b: I2C: cannot write 108 to
> register R21 [ 83.366955] wm8775 1-001b: I2C: cannot write 0c0 to
> register R21 [ 83.372946] wm8775 1-001b: I2C: cannot write 1d4 to
> register R14 [ 83.378749] wm8775 1-001b: I2C: cannot write 1d4 to
> register R15 [ 83.384511] wm8775 1-001b: I2C: cannot write 102 to
> register R21 [ 84.557735] ADDRCONF(NETDEV_UP): wlan0: link is not
> ready [ 84.627866] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> ...skip...
>
>
> ==============================================================
> # lspci -vvv
> ==============================================================
> ...skip...
> 00:14.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Melco Inc Unknown device 052b
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 10
> Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0
> DScale=0 PME-
> ...skip...
>
>
> ==============================================================
> # lspci -vvv -nn
> ==============================================================
> ...skip...
> 00:14.0 Multimedia video controller [0400]: Internext Compression Inc
> iTVC16 (CX23416) MPEG-2 Encoder [4444:0016] (rev 01)
> Subsystem: Melco Inc Unknown device [1154:052b]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 10
> Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0
> DScale=0 PME-
> ...skip...
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

me146983 at oku

May 14, 2008, 11:13 AM

Post #4 of 13 (4600 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

Hans Verkuil wrote:
> On Tuesday 13 May 2008 13:50:18 me146983 [at] oku wrote:
>> 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).

I am happy about all the different suggestions. When the first easy try
with setting "tuner" and "cardtype" did not succeed, i decided to go the
clean route which Hans showed in so much detail (thanks a lot!).

Hans:
> OK, a new card. There we go:
>
> 1) Get the new buffalo tree here:
> http://linuxtv.org/hg/~hverkuil/buffalo/archive/tip.tar.bz2

Worked :-)

> 2) make, make install, and run modprobe ivtv.

"make" had some problems although I worked against a recent 2.6.25.3
kernel. Probably Hans' sources are for a more recent development version?

In detail:

CC [M] /usr/src/buffalo-35e513f58385/v4l/zoran_procfs.o
/usr/src/buffalo-35e513f58385/v4l/zoran_procfs.c: In function
'zoran_proc_init':
/usr/src/buffalo-35e513f58385/v4l/zoran_procfs.c:208: error: implicit
declaration of function 'proc_create_data'
/usr/src/buffalo-35e513f58385/v4l/zoran_procfs.c:208: warning:
assignment makes pointer from integer without a cast
make[3]: *** [/usr/src/buffalo-35e513f58385/v4l/zoran_procfs.o] Error 1

I "fixed" that temporarily by copying the corresponding .c file from my
stock kernel.

CC [M] /usr/src/buffalo-35e513f58385/v4l/mt9m001.o
/usr/src/buffalo-35e513f58385/v4l/mt9m001.c:697: error: array type has
incomplete element type
/usr/src/buffalo-35e513f58385/v4l/mt9m001.c:707: warning: initialization
from incompatible pointer type
/usr/src/buffalo-35e513f58385/v4l/mt9m001.c:709: error: unknown field
'id_table' specified in initializermake[3]: ***
[/usr/src/buffalo-35e513f58385/v4l/mt9m001.o] Error 1
make[2]: *** [_module_/usr/src/buffalo-35e513f58385/v4l] Error 2

I "fixed" that temporarily by commenting the conflicting lines in mt9m001.c.

Both .c files seemed to have nothing to do with my card, so I'm probably
on the safe side here.

"make install" worked.

"modprobe ivtv" complained about disagreeing about versions of symbols,
as my kernel is compiled with CONFIG_MODVERSIONS=y. Workaround:
"modprobe --force-modversion ivtv"

> 3) The card should be autodetected, now see if it works. Start with the
> composite input (select using v4l2-ctl -i2).

The card was detected correctly, but recorded input from the composite
input (3) was just a blank white screen.

dmesg:
[50094.134889] ivtv: Start initialization, version 1.2.1
[50094.140271] ivtv0: Initializing card #0
[50094.140331] ivtv0: Autodetected Buffalo PC-MV5L/PCI card (cx23416 based)
[50094.156142] ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKB] -> GSI
10 (level, low) -> IRQ 10
[50094.354316] cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
[50094.379850] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[50094.391718] xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
[50094.394990] xc2028 1-0061: xc2028/3028 firmware name not set!
[50098.330521] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[50098.436003] ivtv0: Registered device video0 for encoder MPG (4096 kB)
[50099.421890] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[50099.620894] ivtv0: Encoder revision: 0x02060039
[50099.792570] xc2028 1-0061: Loading 80 firmware images from
xc3028-v27.fw, type: xc2028 firmware, ver 2.7
[50099.806164] xc2028 1-0061: Loading firmware for type=BASE (1), id
0000000000000000.
[50101.660563] xc2028 1-0061: Loading firmware for type=(0), id
000000000000b700.
[50101.694287] SCODE (20000000), id 000000000000b700:
[50101.694317] xc2028 1-0061: Loading SCODE for type=SCODE HAS_IF_4500
(60000000), id 0000000000002000.
[50101.734973] xc2028 1-0061: Device is Xceive 3028 version 1.0,
firmware version 2.7
[50101.911301] xc2028 1-0061: Loading firmware for type=(0), id
000000000000b700.
[50101.953105] SCODE (20000000), id 000000000000b700:
[50101.953156] xc2028 1-0061: Loading SCODE for type=SCODE HAS_IF_4500
(60000000), id 0000000000002000.
[50101.994348] xc2028 1-0061: Device is Xceive 3028 version 1.0,
firmware version 2.7
[50102.151392] ivtv0: Registered device video32 for encoder YUV (2048 kB)
[50102.151552] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
[50102.151700] ivtv0: Registered device video24 for encoder PCM (320 kB)
[50102.151730] ivtv0: Initialized card #0: Buffalo PC-MV5L/PCI
[50102.151858] ivtv: End initialization
[50507.745749] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3),
id 0000000000000000.
[50509.617744] (0), id 00000000000000ff:
[50509.617769] xc2028 1-0061: Loading firmware for type=(0), id
0000000100000007.
[50509.653494] SCODE (20000000), id 0000000100000007:
[50509.653526] xc2028 1-0061: Loading SCODE for type=SCODE HAS_IF_5640
(60000000), id 0000000200000007.
[50509.692062] xc2028 1-0061: Device is Xceive 3028 version 1.0,
firmware version 2.7

> 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.

Changing to CX25840_COMPOSITE1 gave me a faint picture with almost no
color and lots of noise on top.

Switching the video mode to PAL ("v4l2-ctl -s pal") did the job! (My
encoder card is currently fed with the moving DVD title menu of a PAL
version of "The Hitchhikers Guide to the Galaxy" in infinite loop --
nice test picture :).

At least I can already record composite video now, cool!

Next step will be the S-Video input, like Hans suggested. This will take
some time because I need to get pysically to the machine and
unplug/replug the video source.

> 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.

(already installed the firmware while compiling; seems to be fine, see
dmesg output above)

> 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.

At least the bigger chips on the card (> about 8 pins) have no such
labeling. These are the chips:

- XCEIVE XC2028ACQ
- CONEXANT CX25843-24Z
- hynix 625A
- CONEXANT MPEG II A/V ENCODER CX23416-22
- CIRRUS 5340CZZ
- 74HC125D
- ATML H726

Kind regards,
Peter

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

hverkuil at xs4all

May 14, 2008, 11:58 AM

Post #5 of 13 (4619 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

On Wednesday 14 May 2008 20:13:16 Peter Brandt wrote:
> Hans Verkuil wrote:
> > On Tuesday 13 May 2008 13:50:18 me146983 [at] oku wrote:
> >> 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).
>
> I am happy about all the different suggestions. When the first easy
> try with setting "tuner" and "cardtype" did not succeed, i decided to
> go the clean route which Hans showed in so much detail (thanks a
> lot!).
>
> Hans:
> > OK, a new card. There we go:
> >
> > 1) Get the new buffalo tree here:
> > http://linuxtv.org/hg/~hverkuil/buffalo/archive/tip.tar.bz2
>
> Worked :-)
>
> > 2) make, make install, and run modprobe ivtv.
>
> "make" had some problems although I worked against a recent 2.6.25.3
> kernel. Probably Hans' sources are for a more recent development
> version?
>
> In detail:
>
> CC [M] /usr/src/buffalo-35e513f58385/v4l/zoran_procfs.o
> /usr/src/buffalo-35e513f58385/v4l/zoran_procfs.c: In function
> 'zoran_proc_init':
> /usr/src/buffalo-35e513f58385/v4l/zoran_procfs.c:208: error: implicit
> declaration of function 'proc_create_data'
> /usr/src/buffalo-35e513f58385/v4l/zoran_procfs.c:208: warning:
> assignment makes pointer from integer without a cast
> make[3]: *** [/usr/src/buffalo-35e513f58385/v4l/zoran_procfs.o] Error
> 1
>
> I "fixed" that temporarily by copying the corresponding .c file from
> my stock kernel.
>
> CC [M] /usr/src/buffalo-35e513f58385/v4l/mt9m001.o
> /usr/src/buffalo-35e513f58385/v4l/mt9m001.c:697: error: array type
> has incomplete element type
> /usr/src/buffalo-35e513f58385/v4l/mt9m001.c:707: warning:
> initialization from incompatible pointer type
> /usr/src/buffalo-35e513f58385/v4l/mt9m001.c:709: error: unknown field
> 'id_table' specified in initializermake[3]: ***
> [/usr/src/buffalo-35e513f58385/v4l/mt9m001.o] Error 1
> make[2]: *** [_module_/usr/src/buffalo-35e513f58385/v4l] Error 2
>
> I "fixed" that temporarily by commenting the conflicting lines in
> mt9m001.c.
>
> Both .c files seemed to have nothing to do with my card, so I'm
> probably on the safe side here.

Correct. You can also run 'make menuconfig' and only configure the cx18
driver. I'm actually using a 2.6.23 kernel. I tried to go to 2.6.25,
but due to some regression I no longer have audio with that kernel :-(

>
> "make install" worked.
>
> "modprobe ivtv" complained about disagreeing about versions of
> symbols, as my kernel is compiled with CONFIG_MODVERSIONS=y.
> Workaround: "modprobe --force-modversion ivtv"

Yup.

>
> > 3) The card should be autodetected, now see if it works. Start with
> > the composite input (select using v4l2-ctl -i2).
>
> The card was detected correctly, but recorded input from the
> composite input (3) was just a blank white screen.
>
> dmesg:
> [50094.134889] ivtv: Start initialization, version 1.2.1
> [50094.140271] ivtv0: Initializing card #0
> [50094.140331] ivtv0: Autodetected Buffalo PC-MV5L/PCI card (cx23416
> based) [50094.156142] ACPI: PCI Interrupt 0000:00:14.0[A] -> Link
> [LNKB] -> GSI 10 (level, low) -> IRQ 10
> [50094.354316] cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c
> driver #0) [50094.379850] tuner 1-0061: chip found @ 0xc2 (ivtv i2c
> driver #0) [50094.391718] xc2028 1-0061: type set to XCeive
> xc2028/xc3028 tuner [50094.394990] xc2028 1-0061: xc2028/3028
> firmware name not set! [50098.330521] cx25840 1-0044: loaded
> v4l-cx25840.fw firmware (16382 bytes) [50098.436003] ivtv0:
> Registered device video0 for encoder MPG (4096 kB) [50099.421890]
> ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> [50099.620894] ivtv0: Encoder revision: 0x02060039
> [50099.792570] xc2028 1-0061: Loading 80 firmware images from
> xc3028-v27.fw, type: xc2028 firmware, ver 2.7
> [50099.806164] xc2028 1-0061: Loading firmware for type=BASE (1), id
> 0000000000000000.
> [50101.660563] xc2028 1-0061: Loading firmware for type=(0), id
> 000000000000b700.
> [50101.694287] SCODE (20000000), id 000000000000b700:
> [50101.694317] xc2028 1-0061: Loading SCODE for type=SCODE
> HAS_IF_4500 (60000000), id 0000000000002000.
> [50101.734973] xc2028 1-0061: Device is Xceive 3028 version 1.0,
> firmware version 2.7
> [50101.911301] xc2028 1-0061: Loading firmware for type=(0), id
> 000000000000b700.
> [50101.953105] SCODE (20000000), id 000000000000b700:
> [50101.953156] xc2028 1-0061: Loading SCODE for type=SCODE
> HAS_IF_4500 (60000000), id 0000000000002000.
> [50101.994348] xc2028 1-0061: Device is Xceive 3028 version 1.0,
> firmware version 2.7
> [50102.151392] ivtv0: Registered device video32 for encoder YUV (2048
> kB) [50102.151552] ivtv0: Registered device vbi0 for encoder VBI
> (1024 kB) [50102.151700] ivtv0: Registered device video24 for encoder
> PCM (320 kB) [50102.151730] ivtv0: Initialized card #0: Buffalo
> PC-MV5L/PCI [50102.151858] ivtv: End initialization
> [50507.745749] xc2028 1-0061: Loading firmware for type=BASE F8MHZ
> (3), id 0000000000000000.
> [50509.617744] (0), id 00000000000000ff:
> [50509.617769] xc2028 1-0061: Loading firmware for type=(0), id
> 0000000100000007.
> [50509.653494] SCODE (20000000), id 0000000100000007:
> [50509.653526] xc2028 1-0061: Loading SCODE for type=SCODE
> HAS_IF_5640 (60000000), id 0000000200000007.
> [50509.692062] xc2028 1-0061: Device is Xceive 3028 version 1.0,
> firmware version 2.7
>
> > 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.
>
> Changing to CX25840_COMPOSITE1 gave me a faint picture with almost no
> color and lots of noise on top.
>
> Switching the video mode to PAL ("v4l2-ctl -s pal") did the job! (My
> encoder card is currently fed with the moving DVD title menu of a PAL
> version of "The Hitchhikers Guide to the Galaxy" in infinite loop --
> nice test picture :).

Ah yes, the default standard selected for these worldwide tuners is
NTSC. I didn't realize that you were in PAL country.

> At least I can already record composite video now, cool!
>
> Next step will be the S-Video input, like Hans suggested. This will
> take some time because I need to get pysically to the machine and
> unplug/replug the video source.
>
> > 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.
>
> (already installed the firmware while compiling; seems to be fine,
> see dmesg output above)

It can be misleading: if the fw still loads correctly after an
rmmod/modprobe then you know the correct pin is selected.

> > 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.
>
> At least the bigger chips on the card (> about 8 pins) have no such
> labeling. These are the chips:
>
> - XCEIVE XC2028ACQ
> - CONEXANT CX25843-24Z
> - hynix 625A
> - CONEXANT MPEG II A/V ENCODER CX23416-22
> - CIRRUS 5340CZZ
> - 74HC125D
> - ATML H726

OK, no special chips then. Good to know.

With a bit of luck it shouldn't be too hard to figure out the full card
definition.

Thanks for your help.

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

me146983 at oku

May 15, 2008, 8:33 AM

Post #6 of 13 (4570 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

Hello Hans and everyone

Hans Verkuil wrote:
> On Wednesday 14 May 2008 20:13:16 Peter Brandt wrote:
>> "make" had some problems although I worked against a recent 2.6.25.3
>> kernel. Probably Hans' sources are for a more recent development
>> version?
>>...
>>
>> Both .c files seemed to have nothing to do with my card, so I'm
>> probably on the safe side here.
>
> Correct. You can also run 'make menuconfig' and only configure the cx18
> driver. I'm actually using a 2.6.23 kernel. I tried to go to 2.6.25,
> but due to some regression I no longer have audio with that kernel :-(

I have not yet checked audio with that kernel. Are you talking about
audio output or audio from the video grabber card?

>> Changing to CX25840_COMPOSITE1 gave me a faint picture with almost no
>> color and lots of noise on top.
>>
>> Switching the video mode to PAL ("v4l2-ctl -s pal") did the job! (My
>> encoder card is currently fed with the moving DVD title menu of a PAL
>> version of "The Hitchhikers Guide to the Galaxy" in infinite loop --
>> nice test picture :).
>
> Ah yes, the default standard selected for these worldwide tuners is
> NTSC. I didn't realize that you were in PAL country.

The card is from Japan and will be used there eventually (=NTSC
country). But I am currently in Europe, doing the setup (=PAL country)
for that box.

>>> 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.

The default CX25840_SVIDEO3 from Hans' card configuration worked, but
only black&white (good picture though).

I checked all the other possiblities:

CX25840_SVIDEO1: black & red noise only
CX25840_SVIDEO2: b/w noise only
CX25840_SVIDEO3: sharp picture but black&white only
CX25840_SVIDEO4: b/w noise only

One other thing that might be important here:
The card has only a S-Video input, no real composite input. For
composite, a small adapter was in the package, which you plug into the
S-Video input and which gives you a composite plug. (This is the
composite input with which I successfully go composite in to work
before, even in color).

>>> 5) Tuner: first get the firmware. See the file
>>> linux/Documentation/video4linux/extract_xc3028.pl for instructions.
>> (already installed the firmware while compiling; seems to be fine,
>> see dmesg output above)
>
> It can be misleading: if the fw still loads correctly after an
> rmmod/modprobe then you know the correct pin is selected.
>
>>> 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.

It seems to be ok. Even after unloading/loading the same module
(version) twice, I get no errors in dmesg.

>>>
>>> 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 },

(tuned to a frequency where there's something in the air)

CX25840_COMPOSITE1: black picture (well, it really is the composite
input...)
CX25840_COMPOSITE2: with antenna input: good picture, color ok, audio ok
CX25840_COMPOSITE3: shows b&w picture of current S-Video input (DVD)
CX25840_COMPOSITE4: some ghost things (images?) on black background; VLC
complains about a missing audio device / filter / pipeline
CX25840_COMPOSITE5: b&w noise
CX25840_COMPOSITE6: black screen with some short white horizontal
stripes sometimes
CX25840_COMPOSITE7: black screen with some white dots sometimes
CX25840_COMPOSITE8: black screen

So it is 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.

The audio settings for the tuner from your source work: CX25840_AUDIO5

>>>
>>> 8) Done!

What is still missing now:
- not yet checked: audio input for composite and S-Video
- color for S-Video

>>> It's a bit annoying to go through all the combinations but it is
>>> the only way to do it.

Well, not sooo bad, really. Essentially a very structured way which will
lead to a result eventually.

> With a bit of luck it shouldn't be too hard to figure out the full card
> definition.

Almost there :-)

> Thanks for your help.

I am the one who has to thank you for your detailed explanation (I never
modified kernel sources before myself, although I did compile some kernels).

Regards,
Peter

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

hverkuil at xs4all

May 15, 2008, 4:00 PM

Post #7 of 13 (4557 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

On Thursday 15 May 2008 17:33, Peter Brandt wrote:
> Hello Hans and everyone
>
> Hans Verkuil wrote:
> > On Wednesday 14 May 2008 20:13:16 Peter Brandt wrote:
> >> "make" had some problems although I worked against a recent
> >> 2.6.25.3 kernel. Probably Hans' sources are for a more recent
> >> development version?
> >>...
> >>
> >> Both .c files seemed to have nothing to do with my card, so I'm
> >> probably on the safe side here.
> >
> > Correct. You can also run 'make menuconfig' and only configure the
> > cx18 driver. I'm actually using a 2.6.23 kernel. I tried to go to
> > 2.6.25, but due to some regression I no longer have audio with
> > that kernel :-(
>
> I have not yet checked audio with that kernel. Are you talking about
> audio output or audio from the video grabber card?

No, that's just the audio chip on my motherboard. Nothing to do with the
cx18 driver.

> >> Changing to CX25840_COMPOSITE1 gave me a faint picture with
> >> almost no color and lots of noise on top.
> >>
> >> Switching the video mode to PAL ("v4l2-ctl -s pal") did the job!
> >> (My encoder card is currently fed with the moving DVD title menu
> >> of a PAL version of "The Hitchhikers Guide to the Galaxy" in
> >> infinite loop -- nice test picture :).
> >
> > Ah yes, the default standard selected for these worldwide tuners
> > is NTSC. I didn't realize that you were in PAL country.
>
> The card is from Japan and will be used there eventually (=NTSC
> country). But I am currently in Europe, doing the setup (=PAL
> country) for that box.
>
> >>> 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.
>
> The default CX25840_SVIDEO3 from Hans' card configuration worked, but
> only black&white (good picture though).

OK, then you need to do one final set of tests: replace SVIDEO3
with 'CX25840_SVIDEO_LUMA3 | CX25840_SVIDEO_CHROMA4' and then try
CHROMA4-8 (you can skip CHROMA7, that's what SVIDEO3 uses).

>
> I checked all the other possiblities:
>
> CX25840_SVIDEO1: black & red noise only
> CX25840_SVIDEO2: b/w noise only
> CX25840_SVIDEO3: sharp picture but black&white only
> CX25840_SVIDEO4: b/w noise only
>
> One other thing that might be important here:
> The card has only a S-Video input, no real composite input. For
> composite, a small adapter was in the package, which you plug into
> the S-Video input and which gives you a composite plug. (This is the
> composite input with which I successfully go composite in to work
> before, even in color).
>
> >>> 5) Tuner: first get the firmware. See the file
> >>> linux/Documentation/video4linux/extract_xc3028.pl for
> >>> instructions.
> >>
> >> (already installed the firmware while compiling; seems to be
> >> fine, see dmesg output above)
> >
> > It can be misleading: if the fw still loads correctly after an
> > rmmod/modprobe then you know the correct pin is selected.
> >
> >>> 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.
>
> It seems to be ok. Even after unloading/loading the same module
> (version) twice, I get no errors in dmesg.
>
> >>> 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 },
>
> (tuned to a frequency where there's something in the air)
>
> CX25840_COMPOSITE1: black picture (well, it really is the composite
> input...)
> CX25840_COMPOSITE2: with antenna input: good picture, color ok, audio
> ok CX25840_COMPOSITE3: shows b&w picture of current S-Video input
> (DVD) CX25840_COMPOSITE4: some ghost things (images?) on black
> background; VLC complains about a missing audio device / filter /
> pipeline
> CX25840_COMPOSITE5: b&w noise
> CX25840_COMPOSITE6: black screen with some short white horizontal
> stripes sometimes
> CX25840_COMPOSITE7: black screen with some white dots sometimes
> CX25840_COMPOSITE8: black screen
>
> So it is 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.
>
> The audio settings for the tuner from your source work:
> CX25840_AUDIO5
>
> >>> 8) Done!
>
> What is still missing now:
> - not yet checked: audio input for composite and S-Video

Audio should be fine: there is no choice there as far as cx25840 inputs
are concerned. You should test it though, sometimes there are gpio
settings required. I hope not, as that's another set of tests cycling
through all combinations.

> - color for S-Video
>
> >>> It's a bit annoying to go through all the combinations but it is
> >>> the only way to do it.
>
> Well, not sooo bad, really. Essentially a very structured way which
> will lead to a result eventually.
>
> > With a bit of luck it shouldn't be too hard to figure out the full
> > card definition.
>
> Almost there :-)
>
> > Thanks for your help.
>
> I am the one who has to thank you for your detailed explanation (I
> never modified kernel sources before myself, although I did compile
> some kernels).

There's no radio on this board? You didn't mention it, so I suspect not.

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

me146983 at oku

May 16, 2008, 9:19 AM

Post #8 of 13 (4529 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

Hans Verkuil wrote:
>> >>> 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.
>>
>> The default CX25840_SVIDEO3 from Hans' card configuration worked, but
>> only black&white (good picture though).
>
> OK, then you need to do one final set of tests: replace SVIDEO3
> with 'CX25840_SVIDEO_LUMA3 | CX25840_SVIDEO_CHROMA4' and then try
> CHROMA4-8 (you can skip CHROMA7, that's what SVIDEO3 uses).

Your first suggestion
CX25840_SVIDEO_LUMA3 | CX25840_SVIDEO_CHROMA4
already did the job. Nice!

>> >>> 8) Done!
>>
>> What is still missing now:
>> - not yet checked: audio input for composite and S-Video
>
> Audio should be fine: there is no choice there as far as cx25840 inputs
> are concerned. You should test it though, sometimes there are gpio
> settings required. I hope not, as that's another set of tests cycling
> through all combinations.

I had audio from the tuner earlier and just now also from the separate
input which is used for S-Video. Have not checked grabbing input from
Composite together with audio yet, but there should be no difference.

>> - color for S-Video

Works now (see above).

> There's no radio on this board? You didn't mention it, so I suspect not.

I don't think so. The japanese leaflet did not talk about radio at all
(as far as i understood it). The card has 5 inputs:

- Antenna
- S-Video (also used for Composite with an adapter)
- Audio (3.5mm to 2x Chinch (red/white) adapter)
- 2.5mm socket
- another 2.5mm socket

Both 2.5mm sockets are marked as "not to use" in the leaflet (I think :).

Thank you very much for patiently guiding me though the process of
finding the correct settings (and for providing the first version of the
card settings)!

My next step will be to incorporate the changes into my kernel's ivtv
module source ASAP, recompile that and reboot. After that I'll check all
video and audio sources once again and let you know about the result.

Regards,
Peter

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

awalls at radix

May 16, 2008, 9:50 AM

Post #9 of 13 (4516 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

On Tue, 2008-05-13 at 20:20 +0200, Hans Verkuil wrote:
> On Tuesday 13 May 2008 13:50:18 me146983 [at] oku 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.

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.

Since cx18 is "bone of ivtv's bone and flesh of ivtv's flesh", this
process can be adapted to apply to getting new cards working for cx18 as
well.

-Andy

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

hverkuil at xs4all

May 16, 2008, 1:04 PM

Post #10 of 13 (4514 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

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 me146983 [at] oku 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
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

hverkuil at xs4all

May 16, 2008, 1:05 PM

Post #11 of 13 (4506 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

On Friday 16 May 2008 18:19, Peter Brandt wrote:
> Hans Verkuil wrote:
> >> >>> 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.
> >>
> >> The default CX25840_SVIDEO3 from Hans' card configuration worked,
> >> but only black&white (good picture though).
> >
> > OK, then you need to do one final set of tests: replace SVIDEO3
> > with 'CX25840_SVIDEO_LUMA3 | CX25840_SVIDEO_CHROMA4' and then try
> > CHROMA4-8 (you can skip CHROMA7, that's what SVIDEO3 uses).
>
> Your first suggestion
> CX25840_SVIDEO_LUMA3 | CX25840_SVIDEO_CHROMA4
> already did the job. Nice!
>
> >> >>> 8) Done!
> >>
> >> What is still missing now:
> >> - not yet checked: audio input for composite and S-Video
> >
> > Audio should be fine: there is no choice there as far as cx25840
> > inputs are concerned. You should test it though, sometimes there
> > are gpio settings required. I hope not, as that's another set of
> > tests cycling through all combinations.
>
> I had audio from the tuner earlier and just now also from the
> separate input which is used for S-Video. Have not checked grabbing
> input from Composite together with audio yet, but there should be no
> difference.
>
> >> - color for S-Video
>
> Works now (see above).
>
> > There's no radio on this board? You didn't mention it, so I suspect
> > not.
>
> I don't think so. The japanese leaflet did not talk about radio at
> all (as far as i understood it). The card has 5 inputs:
>
> - Antenna
> - S-Video (also used for Composite with an adapter)
> - Audio (3.5mm to 2x Chinch (red/white) adapter)
> - 2.5mm socket
> - another 2.5mm socket
>
> Both 2.5mm sockets are marked as "not to use" in the leaflet (I think
> :).
>
> Thank you very much for patiently guiding me though the process of
> finding the correct settings (and for providing the first version of
> the card settings)!
>
> My next step will be to incorporate the changes into my kernel's ivtv
> module source ASAP, recompile that and reboot. After that I'll check
> all video and audio sources once again and let you know about the
> result.

Thanks, if all is well then I'll make an official patch next week and
get it merged. It should appear in 2.6.27 (too late for 2.6.26
unfortunately).

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

awalls at radix

May 16, 2008, 7:07 PM

Post #12 of 13 (4491 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan [In reply to]

On Fri, 2008-05-16 at 22:04 +0200, Hans Verkuil wrote:
> On Friday 16 May 2008 18:50, Andy Walls wrote:

> > 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.

Source comments is the best choice:
- easy to have a commented template
- easy to handle "add line to this array and that array"
- easy to keep in sync with the code

Wiki is the second best choice:
- community can easily contribute lessons learned

v4l-dvb documentation is the worst choice:
- no benefits of the other two options
- not an obvious place: someone must be looking to RTFM

> > 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.

OK.

>
> > Since cx18 is "bone of ivtv's bone and flesh of ivtv's flesh",
>
> How poetic! Much better than 'copy and paste'. :-)

I can't take credit really, so I'll cite my reference properly: metaphor
based on Genesis 2:23. [I can copy and paste too. :) ]

> > 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.

And that is a problem, AFAICT. I dug up the data sheet for the Samsung
chips, and it appears to require pretty good knowledge of how the host
(i.e. the cx23418) intends to drive the chip to set it up properly.

Looking at some PC memory modules, I noticed a small chip off in the
corner that looked like a serial EEPROM - it was. I did some digging
and found out about something called Serial Presence Detect (SPD) which
holds memory device parameters. Slide 28 of this brief shows a picture
of such an EEPROM on a memory module:

http://www.ece.umd.edu/courses/enee759h.S2003/references/config_DDR_Modules.pdf

And this technical note, although not a JEDEC specification or standard,
gives example layouts of SPD tables for several types of memory module:

http://download.micron.com/pdf/technotes/TN_04_42_C.pdf

If only the EEPROMs on these TV boards held similar information.

The windows *.inf file for on of the Toshiba MiniPCI cards actually has
all the DDR parameters in the *inf file. But given the draconian EULA
terms and copyright notices that come with Windows driver packages, I'm
not sure I could give a S-O-B in good conscience pulling the parameters
from the file.

I've seen Mauro often suggest running regspy. I guess that's acceptable
in most cases? I don't know.

I guess knowing the particular DDR chip and having it's datasheet is the
best way to go. In the absence of the proper datasheet, I have no idea
if an iterative or formulaic way to determine DDR parameters is
feasible.

-Andy

> Regards,
>
> Hans
>

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

me146983 at oku

May 18, 2008, 1:58 AM

Post #13 of 13 (4432 views)
Permalink

Re: [UNKNOWN CARD] BUFFALO PC-MV5L/PCI from Japan (solved) [In reply to]

Hans Verkuil wrote:
> On Friday 16 May 2008 18:19, Peter Brandt wrote:
>> Thank you very much for patiently guiding me though the process of
>> finding the correct settings (and for providing the first version of
>> the card settings)!
>>
>> My next step will be to incorporate the changes into my kernel's ivtv
>> module source ASAP, recompile that and reboot. After that I'll check
>> all video and audio sources once again and let you know about the
>> result.
>
> Thanks, if all is well then I'll make an official patch next week and
> get it merged. It should appear in 2.6.27 (too late for 2.6.26
> unfortunately).

Ok, I did the final checks:

I included the modified ivtv-cards.c and ivtv-cards.h in my otherwise
unmodified kernel 2.6.25.3 sources, compiled, created the modules and
installed them.

After a poweroff and reboot the card was correctly detected
automatically. Also, no irregularities in the dmesg output.

Then, I checked the 3 inputs:

* Composite is working (color), including audio from the separate input
plug.
* S-Video is working (color), including audio from the separate input plug.
* The tuner is working (color) (PAL), including audo from the tuner
signal. I had no possibility yet to check NTSC from the tuner, but will
do so in a few weeks in Japan. I'll let you know then.

This is the difference to the original ivtv-cards.c file, which I
received from Hans:

---
buffalo-35e513f58385-unchanged/linux/drivers/media/video/ivtv/ivtv-cards.c
2008-05-14 03:16:39.000000000 +0900
+++ linux-2.6.25.3-buffalo/drivers/media/video/ivtv/ivtv-cards.c
2008-05-17 00:52:29.000000000 +0900
@@ -1152,8 +1152,8 @@
.hw_all = IVTV_HW_CX25840 | IVTV_HW_TUNER,
.video_inputs = {
{ IVTV_CARD_INPUT_VID_TUNER, 0, CX25840_COMPOSITE2 },
- { IVTV_CARD_INPUT_SVIDEO1, 1, CX25840_SVIDEO3 },
- { IVTV_CARD_INPUT_COMPOSITE1, 1, CX25840_COMPOSITE3 },
+ { IVTV_CARD_INPUT_SVIDEO1, 1, CX25840_SVIDEO_LUMA3 |
CX25840_SVIDEO_CHROMA4 },
+ { IVTV_CARD_INPUT_COMPOSITE1, 1, CX25840_COMPOSITE1 },
},
.audio_inputs = {
{ IVTV_CARD_INPUT_AUD_TUNER, CX25840_AUDIO5 },

One more thing:
The card, i.e. the MPEG II encoder chip on the card, is getting quite
hot, so that I can barely touch it. Like all the other chips, the chip
has no heatsink. In your experience, is it normal that the encoder chip
gets so hot?

Thank you very much for your help getting this card to run!

Regards,
Peter

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads