linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ali Abdallah <aliov@xfce.org>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Michael Krufky <mkrufky@kernellabs.com>, linux-media@vger.kernel.org
Subject: Re: Hauppage WinTV-HVR-900H
Date: Fri, 09 Oct 2009 17:31:32 +0000	[thread overview]
Message-ID: <4ACF7374.8090908@xfce.org> (raw)
In-Reply-To: <829197380910090826r5358a8a2p7a13f2915b5adcd8@mail.gmail.com>

Devin Heitmueller wrote:
> On Fri, Oct 9, 2009 at 1:22 PM, Ali Abdallah <aliov@xfce.org> wrote:
>   
>> Screenshots here for TV and S-Video input configuration with TV time.
>>
>> http://ali.blogsite.org/files/tvtime/
>>     
>>> Could you try the S-Video or composite input and see if the picture
>>> quality is still bad (as this well help isolate whether it's a problem
>>> with the tuner chip or the decoder.
>>>
>>>       
>> Same picture quality with S-Video, but with composite there is no picture.
>>     
>
> Ok, this helps alot.  This rules out the tuner and suggests that
> perhaps the video decoder is not being programmed properly.
>
> Could you please send me the output of "dmesg"?  
usb 1-1: new high speed USB device using ehci_hcd and address 15
usb 1-1: configuration #1 chosen from 1 choice
em28xx: New device USB 2881 Video @ 480 Mbps (eb1a:2881, interface 0, 
class 0)
em28xx #0: chip ID is em2882/em2883
em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 81 28 58 12 5c 00 6a 20 6a 00
em28xx #0: i2c eeprom 10: 00 00 04 57 64 57 00 00 60 f4 00 00 02 02 00 00
em28xx #0: i2c eeprom 20: 56 00 01 00 00 00 02 00 b8 00 00 00 5b 1e 00 00
em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 10 02 00 00 00 00 00 00
em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 20 03 55 00 53 00
em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00 31 00 20 00 56 00
em28xx #0: i2c eeprom 80: 69 00 64 00 65 00 6f 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom e0: 5a 00 55 aa 79 55 54 03 00 17 98 01 00 00 00 00
em28xx #0: i2c eeprom f0: 0c 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0xb8846b20
em28xx #0: EEPROM info:
em28xx #0:    AC97 audio (5 sample rates)
em28xx #0:    USB Remote wakeup capable
em28xx #0:    500mA max power
em28xx #0:    Table at 0x04, strings=0x206a, 0x006a, 0x0000
em28xx #0: Identified as Unknown EM2750/28xx video grabber (card=1)
em28xx #0: Your board has no unique USB ID.
em28xx #0: A hint were successfully done, based on eeprom hash.
em28xx #0: This method is not 100% failproof.
em28xx #0: If the board were missdetected, please email this log to:
em28xx #0:     V4L Mailing List  <linux-media@vger.kernel.org>
em28xx #0: Board detected as Pinnacle Hybrid Pro
tvp5150 1-005c: chip found @ 0xb8 (em28xx #0)
tuner 1-0061: chip found @ 0xc2 (em28xx #0)
xc2028 1-0061: creating new instance
xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
usb 1-1: firmware: requesting xc3028-v27.fw
xc2028 1-0061: Loading 80 firmware images from xc3028-v27.fw, type: 
xc2028 firmware, ver 2.7
xc2028 1-0061: Loading firmware for type=BASE (1), id 0000000000000000.
xc2028 1-0061: Loading firmware for type=(0), id 000000000000b700.
SCODE (20000000), id 000000000000b700:
xc2028 1-0061: Loading SCODE for type=MONO SCODE HAS_IF_4320 (60008000), 
id 0000000000008000.
em28xx #0: Config register raw data: 0x58
em28xx #0: AC97 vendor ID = 0xffffffff
em28xx #0: AC97 features = 0x6a90
em28xx #0: Empia 202 AC97 audio processor detected
tvp5150 1-005c: tvp5150am1 detected.
em28xx #0: v4l2 driver version 0.1.2
em28xx #0: V4L2 video device registered as /dev/video0
em28xx #0: V4L2 VBI device registered as /dev/vbi0
xc2028 1-0061: attaching existing instance
xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
em28xx #0/2: xc3028 attached
DVB: registering new adapter (em28xx #0)
DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)...
Successfully loaded em28xx-dvb
tvp5150 1-005c: tvp5150am1 detected.
tvp5150 1-005c: tvp5150am1 detected.
tvp5150 1-005c: tvp5150am1 detected.
xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id 
0000000000000000.
(0), id 0000000000ff0000:
xc2028 1-0061: Loading firmware for type=(0), id 0000000000200000.
xc2028 1-0061: Loading SCODE for type=MONO SCODE HAS_IF_6320 (60008000), 
id 0000000000200000.
tvp5150 1-005c: tvp5150am1 detected.
xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id 
0000000000000000.
(0), id 0000000000ff0000:
xc2028 1-0061: Loading firmware for type=(0), id 0000000000200000.
xc2028 1-0061: Loading SCODE for type=MONO SCODE HAS_IF_6320 (60008000), 
id 0000000000200000.


> I'll see about
> setting up a tree with some additional debugging for you to try out.
>   

Okay i'm ready to try it out.

> Thanks,
>
> Devin
>
>   

Cheers,

Ali.


  reply	other threads:[~2009-10-09 15:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 14:33 Hauppage WinTV-HVR-900H Ali Abdallah
2009-10-08 12:45 ` Michael Krufky
2009-10-08 15:01   ` Ali Abdallah
2009-10-08 14:45     ` Devin Heitmueller
2009-10-08 18:20       ` Ali Abdallah
2009-10-08 16:28         ` Devin Heitmueller
2009-10-08 16:46           ` Markus Rechberger
2009-10-09  7:59             ` Simon Kenyon
2009-10-09  8:21               ` Markus Rechberger
2009-10-09 21:58                 ` Simon Kenyon
2009-10-09 22:24                   ` Markus Rechberger
2009-10-10 11:56                     ` Mauro Carvalho Chehab
2009-10-10 12:05                       ` Markus Rechberger
2009-10-10 12:24                         ` Mauro Carvalho Chehab
2009-10-11  0:03                         ` hermann pitton
2009-10-13 23:52                       ` Bill Davidsen
2009-10-14  9:48                         ` Simon Kenyon
2009-10-14 12:47                           ` James Peters
2009-10-14 15:42                             ` Simon Kenyon
2009-10-14 15:53                               ` James Peters
2009-10-14 19:22                               ` Bill Davidsen
2009-10-15 15:37                                 ` Simon Kenyon
2009-10-08 18:37           ` Ali Abdallah
2009-10-09  9:34           ` Ali Abdallah
2009-10-09 13:29             ` Devin Heitmueller
2009-10-09 15:35               ` Ali Abdallah
2009-10-09 17:22               ` Ali Abdallah
2009-10-09 15:26                 ` Devin Heitmueller
2009-10-09 17:31                   ` Ali Abdallah [this message]
2009-10-14 13:45                   ` Ali Abdallah
2009-10-14 12:30                     ` Mauro Carvalho Chehab
2009-10-14 15:30                       ` Ali Abdallah
2009-10-14 15:02                         ` libv4l does not work! Guilherme Longo
2009-10-14 15:57                           ` Onur Küçük
2009-10-14 16:38                             ` (V4L2_PIX_FMT_SBGGR8) wierd behavior trying to get image from buffer! Guilherme Longo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ACF7374.8090908@xfce.org \
    --to=aliov@xfce.org \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mkrufky@kernellabs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).