Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: devel

IVTV with Toshiba Qosmio Notebooks.

 

 

ivtv devel RSS feed   Index | Next | Previous | View Threaded


dc2rpt at gmx

Aug 7, 2005, 2:39 PM

Post #1 of 3 (3243 views)
Permalink
IVTV with Toshiba Qosmio Notebooks.

Hi,

i'm trying to setup the ivtv-driver for the tv-receiver inside the Toshiba
Qosmio Notebooks. This notebooks have a special mini-pci card inside, which
is very similar to the Happauge PVR-cards.

I could provide some pictures of the card, but i think, attaching to this mail
is not a good idea... :)
Ok, on this cards there are following chips:
- "Conexant MPEG II AV Encoder CX23416-22"
- "Micronas MSP3455G BB V3"
- "Micronas DRX3960A H"
- "Microtune MT 2050F"
The last chip is a chip-tuner of Microtune
(http://www.microtune.com/products/pdf/MT2050_Tuner_IC.pdf), like on the
bt878-cards of Pinnacle and others. I think, this is the biggest difference
to the Happauge-Cards. In the tuner-module of the 2.6.12.2-kernel is already
the support for this tuner included(anlong with the MT2032 with number 33),
but in the tuner-module of ivtv there is only the older MT2032 included.
(BTW, why is ivtv using a special tuner module and not the one of the
kernel ?)

At www.toshiba.de (and also other websites of toshiba) could be a
windows-driver found for the card, with ivtvfwextract.pl i extracted the
firmware of the included .sys-file.

Ok, with ivtv-0.3.7b, the card is recognized as PVR-250 and the drivers seems
to start partly... but the many i2c-errors confuses me, maybe someone could
help ? Ptune.pl an ivtvctl seems to work, but when i use cat /dev/video0...,
i got no output.

I did:
modprobe ivtv tuner=33
and got the output in the syslog:

Aug 7 23:35:32 localhost kernel: ivtv: ==================== START INIT IVTV
====================
Aug 7 23:35:32 localhost kernel: ivtv: version 0.3.7 (b) loading
Aug 7 23:35:32 localhost kernel: ivtv: Linux version: 2.6.12.2 preempt
PENTIUMM gcc-3.3
Aug 7 23:35:32 localhost kernel: ivtv: In case of problems please include the
debug info
Aug 7 23:35:32 localhost kernel: ivtv: between the START INIT IVTV and END
INIT IVTV lines when
Aug 7 23:35:32 localhost kernel: ivtv: mailing the ivtv-devel mailinglist.
Aug 7 23:35:32 localhost kernel: ivtv: Unknown card: vendor/device:
4444/0016, subsystem vendor/device: 1179/0001
Aug 7 23:35:32 localhost kernel: ivtv: Defaulting to WinTV PVR 250 card
Aug 7 23:35:32 localhost kernel: ivtv: Please mail the vendor/device and
subsystem vendor/device IDs and what kind of
Aug 7 23:35:32 localhost kernel: ivtv: card you have to the ivtv-devel
mailinglist: http://sourceforge.net/projects/ivtv
Aug 7 23:35:32 localhost kernel: ivtv: Prefix your subject line with [UNKNOWN
CARD].
Aug 7 23:35:32 localhost kernel: ivtv: Found an iTVC16 based chip
Aug 7 23:35:32 localhost kernel: ACPI: PCI Interrupt 0000:02:09.0[A] -> Link
[LNKD] -> GSI 11 (level, low) -> IRQ 11
Aug 7 23:35:32 localhost kernel: ivtv: i2c client addr: 0x50 not found for
command 0x0!
Aug 7 23:35:32 localhost kernel: ivtv: Error -19 reading Hauppauge eeprom.
Aug 7 23:35:32 localhost kernel: ivtv: Possible causes: the tveeprom module
was not loaded, or
Aug 7 23:35:32 localhost kernel: ivtv: the eeprom kernel module was loaded
before the tveeprom module.
Aug 7 23:35:32 localhost kernel: tuner: Ignoring new-style parameters in
presence of obsolete ones
Aug 7 23:35:32 localhost kernel: saa7115: starting probe for adapter ivtv i2c
driver #0 (0x10005)
Aug 7 23:35:32 localhost kernel: msp34xx: ivtv version
Aug 7 23:35:32 localhost kernel: msp34xx: init: chip=MSP3455G-B8, has NICAM
support, simple (D) mode, simpler (G) no-thread mode
Aug 7 23:35:32 localhost kernel: msp34xx: $Id$ compiled on: Aug 5 2005
21:35:13
Aug 7 23:35:32 localhost kernel: ivtv: i2c attach [client=MSP3455G-B8,ok]
Aug 7 23:35:32 localhost kernel: ivtv: Could not detect tuner standard,
defaulting to NTSC.
Aug 7 23:35:33 localhost kernel: ivtv: Encoder revision: 0x02050424
Aug 7 23:35:33 localhost kernel: ivtv: Encoder Firmware can be buggy, use
version 0x02040011!!!!
Aug 7 23:35:33 localhost kernel: ivtv: Configuring WinTV PVR 250 card with 4
streams
Aug 7 23:35:33 localhost kernel: ivtv: Registered v4l2 device for encoder
MPEG minor 0
Aug 7 23:35:33 localhost kernel: ivtv: Create DMA encoder MPEG stream: 0 x
32768 buffers (0KB total)
Aug 7 23:35:33 localhost kernel: ivtv: Registered v4l2 device for encoder YUV
minor 32
Aug 7 23:35:33 localhost kernel: ivtv: Create DMA encoder YUV stream: 0 x
10800 buffers (0KB total)
Aug 7 23:35:33 localhost kernel: ivtv: Registered v4l2 device for encoder VBI
minor 224
Aug 7 23:35:33 localhost kernel: ivtv: Create DMA encoder VBI stream: 0 x
8736 buffers (0KB total)
Aug 7 23:35:33 localhost kernel: ivtv: Registered v4l2 device for encoder PCM
audio minor 24
Aug 7 23:35:33 localhost kernel: ivtv: Create DMA encoder PCM audio stream: 0
x 4608 buffers (0KB total)
Aug 7 23:35:33 localhost kernel: ivtv: Setting Tuner 33
Aug 7 23:35:33 localhost kernel: ivtv: i2c client id: 0x02 not found!
Aug 7 23:35:33 localhost kernel: ivtv: i2c client addr: 0x21 not found for
command 0x40046403!
Aug 7 23:35:33 localhost kernel: ivtv: i2c client id: 0x02 not found!
Aug 7 23:35:33 localhost kernel: ivtv: i2c client addr: 0x21 not found for
command 0x40046404!
Aug 7 23:35:33 localhost kernel: ivtv: Setting audio matrix to input 3,
output 1
Aug 7 23:35:33 localhost kernel: ivtv: ivtv_enc_thread: pid = 5260, itv =
0xe0bcc1a0
Aug 7 23:35:33 localhost kernel: ivtv: ivtv_enc_vbi_thread: pid = 5261, itv =
0xe0bcc1a0
Aug 7 23:35:33 localhost kernel: ivtv: Switching standard to NTSC.
Aug 7 23:35:33 localhost kernel: ivtv: i2c client id: 0x02 not found!
Aug 7 23:35:34 localhost kernel: ivtv: i2c client addr: 0x21 not found for
command 0x40046403!
Aug 7 23:35:34 localhost kernel: ivtv: Initialized WinTV PVR 250, card #0
Aug 7 23:35:34 localhost kernel: ivtv: ==================== END INIT IVTV
====================


The output of lspci is:
lspci -vv
(...)
0000:02:09.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)
Subsystem: Toshiba America Info Systems: Unknown device 0001
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 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 9c000000 (32-bit, prefetchable)
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-
(...)


Ok, i would send you as much infos you need, maybe this could help to make the
ivtv-driver also supporting the Qosmio's

cu Thomas


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


dc2rpt at gmx

Aug 22, 2005, 11:36 AM

Post #2 of 3 (3146 views)
Permalink
Re: IVTV with Toshiba Qosmio Notebooks. [In reply to]

Hi.

I still think, using the ivtv-driver for the tv-tuner of the Qosmio notebooks
of toshiba would be a good idea. :) So i collected some informations, maybe
the developers could need that.

The Qosmio series of Toshiba is a notebook with a build tv-tuner on a
minipci-card, which is quite similar to the Happauge PVR-x50. In all
notebooks (Qosmio E10, F10, F20, G10, G20) the same card is used.

So, maybe these are helpful informations and Hans or Chris or somebody else
say some words, if its possible to enhance the ivtv-driver to support the
Qosmio-Cards.

If it helps, i could provide a shell-acount on a machine, where such a card is
in use, because they are not seperate to buy.

I disasembled my notebook to have a look on the card:
Hardware:

A complete list of the chips on the board.

- Microtune MT2050
Chip-Tuner, converts the HF to the baseband-signal. It is detected by the
tuner-module in ivtv and used in some other bt8x8-boards.

- Micronas DRX 3960A
The IF-Modulator, it demodulates the baseband-signal to the cvbs-signal and
sound output.
I don't find which chip is used one the Happauge Boards instead. But i think,
there is only some short i2c-init necessary.

- NEC D64031
It does some "Ghostimage"-reduction on the analog cvbs-signal. There is a
i2c-control, but the chip is also used on some other bt8x8-boards.

- NEC D64011
That is the video decoder on the board. The Happauge boards use the SAA7115
instead. It converts the analog cvbs-signal to the digital signal. There is
also a i2c-control, maybe someone could got the command-list from NEC.

- Conexant CX23416-22
Its the MPEG-Encoder, like on the Happauge boards.

- Micronas MSP3455G
That is the sound processor, like it also used on the other bt8x8-boards.

On the board is also some RAM and i think a I2C-Eeprom, but they are below the
shielding-plate.

Ok, i hope, this could give some overview about the hardware and the signal
chain.

I think the biggest problem is the video decoder, but maybe i could get some
informations with a i2c-sniffer, when no datasheet is provided by NEC.

Software:

ivtv-0.3.7h starts quite nice, but lacks of support for the different chips:
I extracted the firmware of the toshiba windows-driver.

Aug 22 17:26:09 localhost kernel: Linux video capture interface: v1.00
Aug 22 17:26:09 localhost kernel: ivtv: ==================== START INIT IVTV
====================
Aug 22 17:26:09 localhost kernel: ivtv: version 0.3.7 (h) loading
Aug 22 17:26:09 localhost kernel: ivtv: Linux version: 2.6.12.5 preempt
PENTIUMM gcc-3.3
Aug 22 17:26:09 localhost kernel: ivtv: In case of problems please include the
debug info
Aug 22 17:26:09 localhost kernel: ivtv: between the START INIT IVTV and END
INIT IVTV lines when
Aug 22 17:26:09 localhost kernel: ivtv: mailing the ivtv-devel mailinglist.
Aug 22 17:26:09 localhost kernel: ivtv: Unknown card: vendor/device: 4444/0016
Aug 22 17:26:09 localhost kernel: ivtv: subsystem vendor/device:
1179/0001
Aug 22 17:26:09 localhost kernel: ivtv: iTVC16 based
Aug 22 17:26:09 localhost kernel: ivtv: Defaulting to WinTV PVR 250 card
Aug 22 17:26:09 localhost kernel: ivtv: Please mail the vendor/device and
subsystem vendor/device IDs and what kind of
Aug 22 17:26:09 localhost kernel: ivtv: card you have to the ivtv-devel
mailinglist: http://sourceforge.net/projects/ivtv
Aug 22 17:26:09 localhost kernel: ivtv: Prefix your subject line with [UNKNOWN
CARD].
Aug 22 17:26:09 localhost kernel: ACPI: PCI Interrupt 0000:02:09.0[A] -> Link
[LNKD] -> GSI 11 (level, low) -> IRQ 11
Aug 22 17:26:09 localhost kernel: ivtv warning: i2c client addr: 0x50 not
found for command 0x0!
Aug 22 17:26:09 localhost kernel: ivtv: Error -19 reading Hauppauge eeprom.
Aug 22 17:26:09 localhost kernel: ivtv: Possible causes: the tveeprom module
was not loaded, or
Aug 22 17:26:09 localhost kernel: ivtv: the eeprom kernel module was loaded
before the tveeprom module.
Aug 22 17:26:09 localhost kernel: tuner: Ignoring new-style parameters in
presence of obsolete ones
Aug 22 17:26:09 localhost kernel: tuner: chip found at addr 0xc0 i2c-bus ivtv
i2c driver #0
Aug 22 17:26:09 localhost kernel: Chip ID is not zero. It is not a TEA5767
Aug 22 17:26:09 localhost kernel: ivtv: i2c attach to card #0 ok
[client=(tunerunset), addr=60]
Aug 22 17:26:09 localhost kernel: msp34xx: ivtv version
Aug 22 17:26:09 localhost kernel: msp34xx: init: chip=MSP3455G-B8, has NICAM
support, simple (D) mode, simpler (G) no-thread mode
Aug 22 17:26:09 localhost kernel: msp34xx: $Id$ compiled on: Aug 22 2005
17:21:41
Aug 22 17:26:09 localhost kernel: ivtv: i2c attach to card #0 ok
[client=MSP3455G-B8, addr=40]
Aug 22 17:26:09 localhost kernel: ivtv: Could not detect tuner standard,
defaulting to NTSC.
Aug 22 17:26:10 localhost kernel: ivtv: Encoder revision: 0x02050424
Aug 22 17:26:10 localhost kernel: ivtv warning: Encoder Firmware can be buggy,
use version 0x02040011!!!!
Aug 22 17:26:10 localhost kernel: ivtv: Create DMA encoder MPEG stream: 0 x
32768 buffers (0KB total)
Aug 22 17:26:10 localhost kernel: ivtv: Create DMA encoder YUV stream: 0 x
10800 buffers (0KB total)
Aug 22 17:26:10 localhost kernel: ivtv: Create DMA encoder VBI stream: 0 x
17472 buffers (0KB total)
Aug 22 17:26:10 localhost kernel: ivtv: Create DMA encoder PCM audio stream: 0
x 4608 buffers (0KB total)
Aug 22 17:26:10 localhost kernel: tuner: type set to 33 (MT20xx universal) by
ivtv i2c driver #0
Aug 22 17:26:10 localhost kernel: tuner: microtune: companycode=3cbf part=42
rev=2f
Aug 22 17:26:10 localhost kernel: tuner: microtune MT2050 found, OK
Aug 22 17:26:10 localhost kernel: ivtv warning: i2c client addr: 0x21 not
found for command 0x40046403!
Aug 22 17:26:10 localhost kernel: ivtv warning: i2c client addr: 0x21 not
found for command 0x40046404!
Aug 22 17:26:10 localhost kernel: ivtv warning: i2c client addr: 0x21 not
found for command 0x40046403!
Aug 22 17:26:10 localhost kernel: ivtv warning: i2c client addr: 0x21 not
found for command 0x40046406!
Aug 22 17:26:11 localhost kernel: ivtv warning: i2c client addr: 0x21 not
found for command 0x40046406!
Aug 22 17:26:11 localhost kernel: ivtv: Initialized WinTV PVR 250, card #0
Aug 22 17:26:11 localhost kernel: ivtv: ==================== END INIT IVTV
====================

On the i2c-bus are the following devices:

quasimodo ~ # i2cdetect -a 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0.
I will probe address range 0x00-0x7f.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX 12 XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: UU 41 XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: XX XX XX XX XX XX XX XX XX XX XX XX 5c XX XX XX
60: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

quasimodo ~ # lspci -vv
[...]
0000:02:09.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)
Subsystem: Toshiba America Info Systems: Unknown device 0001
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 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 9c000000 (32-bit, prefetchable)
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-





cu Thomas


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


hverkuil at xs4all

Aug 22, 2005, 1:23 PM

Post #3 of 3 (3092 views)
Permalink
Re: IVTV with Toshiba Qosmio Notebooks. [In reply to]

On Monday 22 August 2005 20:36, Thomas Pinz wrote:
> Hi.
>
> I still think, using the ivtv-driver for the tv-tuner of the Qosmio notebooks
> of toshiba would be a good idea. :) So i collected some informations, maybe
> the developers could need that.
>
> The Qosmio series of Toshiba is a notebook with a build tv-tuner on a
> minipci-card, which is quite similar to the Happauge PVR-x50. In all
> notebooks (Qosmio E10, F10, F20, G10, G20) the same card is used.
>
> So, maybe these are helpful informations and Hans or Chris or somebody else
> say some words, if its possible to enhance the ivtv-driver to support the
> Qosmio-Cards.
>
> If it helps, i could provide a shell-acount on a machine, where such a card is
> in use, because they are not seperate to buy.

That's not enough, you need to have such hardware on hand.

>
> I disasembled my notebook to have a look on the card:
> Hardware:
>
> A complete list of the chips on the board.
>
> - Microtune MT2050
> Chip-Tuner, converts the HF to the baseband-signal. It is detected by the
> tuner-module in ivtv and used in some other bt8x8-boards.
>
> - Micronas DRX 3960A
> The IF-Modulator, it demodulates the baseband-signal to the cvbs-signal and
> sound output.
> I don't find which chip is used one the Happauge Boards instead. But i think,
> there is only some short i2c-init necessary.

Datasheets are generally easily available from their website.

> - NEC D64031
> It does some "Ghostimage"-reduction on the analog cvbs-signal. There is a
> i2c-control, but the chip is also used on some other bt8x8-boards.
>
> - NEC D64011
> That is the video decoder on the board. The Happauge boards use the SAA7115
> instead. It converts the analog cvbs-signal to the digital signal. There is
> also a i2c-control, maybe someone could got the command-list from NEC.

You need a good datasheet for this.

> I think the biggest problem is the video decoder, but maybe i could get some
> informations with a i2c-sniffer, when no datasheet is provided by NEC.

With a datasheet you stand a reasonably chance of making it work. Otherwise it's
probably not worth the time.

Hans


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ivtv devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.