public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Steven Toth <stoth@kernellabs.com>
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] saa7164: convert to the control framework
Date: Fri, 28 Aug 2015 15:23:43 +0200	[thread overview]
Message-ID: <55E060DF.3030202@xs4all.nl> (raw)
In-Reply-To: <CALzAhNUMN6BhNZQgGE57-ujoi2O1-baVW_AWFYep7Xd0b4Okrg@mail.gmail.com>

On 08/28/2015 02:44 PM, Steven Toth wrote:
>>> Send me your shipping address _privately_, I talk to Hauppauge about a
>>> replacement.
>>>
>>
>> No need, I managed to get it working if I use a PCI-to-PCIe adapter card. Very
>> strange, it won't work in the PCIe slot of my motherboard, but using the PCI slot
>> and that adapter it works fine.
> 
> Excellent.
> 
>>
>> It's good that it was tested since the menu control creation code was wrong.
> 
> Ahh.
> 
>>
>> One thing that is very confusing to me: I have this board:
>>
>> [ 1878.280918] CORE saa7164[0]: subsystem: 0070:8900, board: Hauppauge WinTV-HVR2200 [card=5,autodetected]
>> [ 1878.280928] saa7164[0]/0: found at 0000:09:00.0, rev: 129, irq: 18, latency: 0, mmio: 0xfb800000
>> [ 1878.327399] tveeprom 14-0000: Hauppauge model 89519, rev B2F2, serial# 4029789519
>> [ 1878.327405] tveeprom 14-0000: MAC address is 00:0d:fe:31:b5:4f
>> [ 1878.327409] tveeprom 14-0000: tuner model is NXP 18271C2_716x (idx 152, type 4)
>> [ 1878.327413] tveeprom 14-0000: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
>> [ 1878.327416] tveeprom 14-0000: audio processor is SAA7164 (idx 43)
>> [ 1878.327418] tveeprom 14-0000: decoder processor is CX23887A (idx 39)
>> [ 1878.327420] tveeprom 14-0000: has radio
>> [ 1878.327423] saa7164[0]: Hauppauge eeprom: model=89519
>>
>> but the default firmware with size 4919072 fails to work (image corrupt), instead
>> I need to use the firmware with size 4038864 (v4l-saa7164-1.0.3-3.fw).
>>
>> For that I have to patch the driver.
> 
> Take a look at your board, on the main large PCIe IC, its probably
> marked as either a REV2 or a REV3, or a -02 or -03, what do you have?
> 
> I suspect you have a rev-02 chip. Not many of them go out into
> production. (A few thousand, compared to significantly more -03
> chips).

The text on the chip is:

SAA7164E/2
P60962.00	10
ESG07271Y

I suspect the /2 means REV2.

Regards,

	Hans

  reply	other threads:[~2015-08-28 13:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 14:08 [PATCH] saa7164: convert to the control framework Hans Verkuil
2015-08-22  7:24 ` Ricardo Ribalda Delgado
2015-08-22 10:47   ` Hans Verkuil
2015-08-22 12:06     ` Steven Toth
2015-08-22 12:46       ` Hans Verkuil
2015-08-26 13:08         ` Steven Toth
2015-08-26 13:13           ` Hans Verkuil
2015-08-26 13:23             ` Steven Toth
2015-08-28  7:59               ` Hans Verkuil
2015-08-28  8:25                 ` Hans Verkuil
2015-08-28 12:47                   ` Steven Toth
2015-08-28 12:44                 ` Steven Toth
2015-08-28 13:23                   ` Hans Verkuil [this message]
2015-08-28 14:36                     ` Steven Toth

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=55E060DF.3030202@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=ricardo.ribalda@gmail.com \
    --cc=stoth@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