Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-10-04 Thread Ian Goldberg 
On Sun, Sep 18, 2016 at 11:22:03AM -0500, is...@isely.net wrote:
> On Sun, 18 Sep 2016, Ian Goldberg wrote:
> 
> > On Sun, Sep 18, 2016 at 03:37:00AM +, Gary Buhrmaster wrote:
> > > Lastly, the 1975 is more like two devices than one.
> > > It has both the ATSC and DVB demods on board,
> > > and likely (although I have no personal experience)
> > > needs two sets of firmware blobs (one for each
> > > demod)?
> > 
> > It does come with two firmware blobs:
> > 
> > 16382 Mar  2  2014 v4l-cx25840.fw
> > 16384 Jan  5  2015 v4l-pvrusb2-160xxx-01.fw
> 
> There's one missing.
> 
> v4l-cx25840.fw is needed for the cx25840 chip (which handles analog 
> demodulation).  Earlier pvrusb2 devices (very early - the model 29xxx 
> series) had a different part which didn't need this firmware.  This 
> firmware, btw, is not specific to the pvrusb2 driver.  Any other v4l 
> device which uses this chip generally needs the same firmware.
> 
> v4l-pvrusb2-160xxx-01.fw is not a name that the "official" pvrusb2 
> driver uses but it probably corresponds to the Cypress FX2 firmware 
> needed in the HVR-1975 (this part is effectively the controller for 
> everything else).  This firmware blob is very specific to the device in 
> question - only the pvrusb2 driver will ever care about it.
> 
> To handle analog video (e.g. composite / s-video input or pre-digital 
> TV) there is another chip present which has its own processor and 
> performs the mpeg2 encoding step.  For digital video this part should 
> become a pass-through (memory is foggy there).  It has a required 
> firmware blob, that without it, the part will not work.

I put all the firmware files in the tarball into /lib/firmware, and for
simplicity, disconnected one of the HVR devices.

Now, it is capturing content aparently properly, so yay for step 1!

The blaster still doesn't work, though, and the Hauppauge people got
back to me, saying:

> There was no blasting support in the Linux driver.

Well, f***.  That makes these devices pretty useless to me, unless
either a) I somehow rig up a separate pair of blasters controllable from
USB, or b) blasting support gets added to the driver.

Does your 1950 driver support the blaster?  How hard would it be to get
their 1975 driver to support it?  (Again, I'm happy to help with kernel
hacking.)

> > [Note that I'm happy to help with some kernel hacking, if that's
> > useful for debugging.]
> 
> I need to analyze that patch hvr-1975 patch.  That's going to take some 
> time.  In the mean time, anyone that can help get its copyright status 
> cleared up will of course clear the way for it to be permanently merged 
> into the pvrusb2 driver, which in the end is really the right thing to 
> be done.  If anyone is talking to Hauppauge, please ask them to contact 
> me.  I've talked to them before, but the contact I used to work with 
> there has long since moved on to greener pastures.

Hauppauge specifically told me they cannot put me in touch with the
linux developers directly, but since it's your copyright, maybe you'd
have more luck?  I can put you in contact with the support person I've
been talking to, if you like.

   - Ian
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-18 Thread Ian Goldberg 
On Sun, Sep 18, 2016 at 03:37:00AM +, Gary Buhrmaster wrote:
> Lastly, the 1975 is more like two devices than one.
> It has both the ATSC and DVB demods on board,
> and likely (although I have no personal experience)
> needs two sets of firmware blobs (one for each
> demod)?

It does come with two firmware blobs:

16382 Mar  2  2014 v4l-cx25840.fw
16384 Jan  5  2015 v4l-pvrusb2-160xxx-01.fw

In kern.log, I do see lines like this:

cx25840 7-0044: loaded v4l-cx25840.fw firmware (16382 bytes)

and lines like this:

pvrusb2: firmware2 upload transfer failure

but nothing specifically naming the file v4l-pvrusb2-160xxx-01.fw.

[Note that I'm happy to help with some kernel hacking, if that's
useful for debugging.]

Thanks,

   - Ian
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread Gary Buhrmaster 
On Sun, Sep 18, 2016 at 2:30 AM,   wrote:
>
> Ian:
>
> Wait a second.  Now I'm confused.  Are you or are not using the pvrusb2
> driver?  The error you quoted was definitely phrasing that would have
> come from the pvrusb2 driver.  If you're using something else entirely
> different I'd be VERY curious know why the resemblence.
>
> Also - to others here - I'm confused about something else.  This sounds
> like we're talking about 3 drivers:
>
> 1. The pvrusb2 driver, in the kernel mainline.
>
> 2. Something on the Hauppauge web site, apparently freely accessible.
>
> 3. Something from Hauppauge that can't be acquired without an NDA.
>
> Is this correct?  Anyone, chime in.

I think part of the issue is that Hauppauge has many
different devices.

For (3), there have been rumors for years that Hauppauge
either had (or re-licensed from one of the few competent
vendors for such codes) various drivers for their devices
(some of which have nothing to do with the pvrusb2 series)
to support vendors who needed official support (not only
in Linux, but other OS's).  At one point a NDA license
was needed for any of their new chipset design devices
(and presumably payment of fees).

Hauppauge had posted some drivers for some of their
devices which clearly had proprietary licenses in the
headers.  When I saw such a license, I stopped reading
the code (and have not gone back to look at anything
newer).

At some point Hauppauge offered their "freely
downloadable" patch for some (different?) set of devices,
which from other discussions is not merge-able upstream
(at least not in the current state; I have no idea about
whether licensing is part of that).

Lastly, the 1975 is more like two devices than one.
It has both the ATSC and DVB demods on board,
and likely (although I have no personal experience)
needs two sets of firmware blobs (one for each
demod)?
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread Ian Goldberg 
On Sat, Sep 17, 2016 at 09:55:33PM -0500, is...@isely.net wrote:
> On Sat, 17 Sep 2016, Ian Goldberg wrote:
> 
> > 
> > Hauppauge a little while back posted the #3 thing (that used to require
> > the NDA) to their web page, no more NDA required.  So #2 and #3 are the
> > same thing now.
> > 
> > That thing is a *patch* to the kernel mainline pvrusb2 driver.  To
> > install it, one has to download the kernel source, apply the patch
> > (which applied perfectly cleanly), and rebuild.
> > 
> > You can look at the patch yourself:
> > http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz
> 
> Got it.  And looked at it.
> 
> This is interesting, if #2 is what #3 used to be, then when #3 existed 
> it was DEFINITELY a copyright infringement - because they would have 
> been combining my GPL'ed code with their changes and then hiding it all 
> behind an NDA.  Very, very uncool.

To be fair, I never did the NDA thing myself, of course; I'm just
assuming it was the same because of the note on this page:

https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1950

It sounds from there like the NDA got you a kernel patch (maybe this
very one, but maybe not).

> So I at least hope you're right that #3 is history and #2 is the 
> present.  Still need to hear from them about that patch's licensing 
> status before I can try to merge anything :-(

I received one useful response from supp...@hauppauge.com a while back,
but haven't received a reply from them about this particular issue.

   - Ian
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread isely 
On Mon, 12 Sep 2016, Roger wrote:

   [...]

> 
> I'll take a gander, likely one or two chips (or maybe some of the code 
> for the firmware) have questionable disclosures attached during the 
> engineering/manufacturing process.  And may or may not be provided 
> openly at a later date.  But then I stumble back on this thought, and 
> if it's just the firmwares, we should be able to extract them from the 
> Windows' driver package.

Please do take a gander.

  -Mike

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread isely 
On Sat, 17 Sep 2016, Ian Goldberg wrote:

> 
> Hauppauge a little while back posted the #3 thing (that used to require
> the NDA) to their web page, no more NDA required.  So #2 and #3 are the
> same thing now.
> 
> That thing is a *patch* to the kernel mainline pvrusb2 driver.  To
> install it, one has to download the kernel source, apply the patch
> (which applied perfectly cleanly), and rebuild.
> 
> You can look at the patch yourself:
> http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz

Got it.  And looked at it.

This is interesting, if #2 is what #3 used to be, then when #3 existed 
it was DEFINITELY a copyright infringement - because they would have 
been combining my GPL'ed code with their changes and then hiding it all 
behind an NDA.  Very, very uncool.

So I at least hope you're right that #3 is history and #2 is the 
present.  Still need to hear from them about that patch's licensing 
status before I can try to merge anything :-(

  -Mike


-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread isely 
On Tue, 13 Sep 2016, Gary Buhrmaster wrote:

> On Mon, Sep 12, 2016 at 10:35 PM,   wrote:
> 
> > I know basically nothing about the HVR-1975.
> 
> As I understand it, the HVR-1975 is essentially
> a "one size fits all" redesign of the basic HVR-1900
> and the HVR-1950/1955 which is compatible with
> both US and DVB standards [mostly for commercial
> embedded solutions that want one SKU for either
> location (it actually contains two demods)].

OK, this helps a lot...

> 
> Hauppuage (last I knew) reportedly offered an out
> of tree driver on their website for the HVR-1975,
> but (again, last I knew) it was never submitted
> upstream (it was reported some of the code
> included non-GPL copyright, and I presume
> it could not be re-licensed).

There's no copyright attribution at all for the patch.  I can't accept 
it even as-is right now because of this.  Scanning the patch quickly, I 
didn't see anything jump out that might "smell" like any kind of secret 
sauce complicating a copyright.  But "smell" is not a good legal test, 
unfortunately...

  -Mike

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread Ian Goldberg 
On Sat, Sep 17, 2016 at 09:30:34PM -0500, is...@isely.net wrote:
> 
> Ian:
> 
> Wait a second.  Now I'm confused.  Are you or are not using the pvrusb2 
> driver?  The error you quoted was definitely phrasing that would have 
> come from the pvrusb2 driver.  If you're using something else entirely 
> different I'd be VERY curious know why the resemblence.
> 
> Also - to others here - I'm confused about something else.  This sounds 
> like we're talking about 3 drivers:
> 
> 1. The pvrusb2 driver, in the kernel mainline.
> 
> 2. Something on the Hauppauge web site, apparently freely accessible.
> 
> 3. Something from Hauppauge that can't be acquired without an NDA.
> 
> Is this correct?  Anyone, chime in.
> 
>   -Mike

Hauppauge a little while back posted the #3 thing (that used to require
the NDA) to their web page, no more NDA required.  So #2 and #3 are the
same thing now.

That thing is a *patch* to the kernel mainline pvrusb2 driver.  To
install it, one has to download the kernel source, apply the patch
(which applied perfectly cleanly), and rebuild.

You can look at the patch yourself:
http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz

   - Ian
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread isely 

OK, I looked at case #2 and it's a ginormous patch against a few v4l 
chip-level drivers and additional configuration definition(s) for the 
pvrusb2 driver to support this device.  In addition, the patch appears 
to be modifying functional logic in the driver itself, which may or may 
not be harmful to other pvrusb2-driven devices (the other bits follow 
the pattern I had laid down for adding hardware support so those parts 
are pretty safe).

I need to go through this in detail and it should be formally merged 
with the pvrusb2 driver.  If anyone can find out who has copyright 
authority over this (presumably Hauppauge and I'd love to hear from them 
about this), that needs to be sorted before it can be accepted.  
There's no copyright info with the patch AFAICT.

It would have been useful if I had been contacted directly by Hauppauge 
about this.  But admittedly I've been out of the loop for a while so 
maybe they did and I didn't see it or they figured I was MIA.

I see that this big patch also includes firmware blobs, but nothing for 
any mpeg2 encoder on-board, so that would not help the problem that 
started this thread.

The subject of this thread "(with official drivers)" - I'd say that 
term is questionable at best.  The patch might be from Hauppauge but it 
really has the feel of something thrown over the fence and not really 
"supported".

No idea still about case #3 (NDA-requiring case).

  -Mike


On Sat, 17 Sep 2016, is...@isely.net wrote:

> 
> Ian:
> 
> Wait a second.  Now I'm confused.  Are you or are not using the pvrusb2 
> driver?  The error you quoted was definitely phrasing that would have 
> come from the pvrusb2 driver.  If you're using something else entirely 
> different I'd be VERY curious know why the resemblence.
> 
> Also - to others here - I'm confused about something else.  This sounds 
> like we're talking about 3 drivers:
> 
> 1. The pvrusb2 driver, in the kernel mainline.
> 
> 2. Something on the Hauppauge web site, apparently freely accessible.
> 
> 3. Something from Hauppauge that can't be acquired without an NDA.
> 
> Is this correct?  Anyone, chime in.
> 
>   -Mike
> 
> 
> On Mon, 12 Sep 2016, Ian Goldberg wrote:
> 
> > On Tue, Sep 13, 2016 at 12:37:25AM +, Gary Buhrmaster wrote:
> > > On Mon, Sep 12, 2016 at 10:35 PM,   wrote:
> > > 
> > > > I know basically nothing about the HVR-1975.
> > > 
> > > As I understand it, the HVR-1975 is essentially
> > > a "one size fits all" redesign of the basic HVR-1900
> > > and the HVR-1950/1955 which is compatible with
> > > both US and DVB standards [mostly for commercial
> > > embedded solutions that want one SKU for either
> > > location (it actually contains two demods)].
> > > 
> > > Hauppuage (last I knew) reportedly offered an out
> > > of tree driver on their website for the HVR-1975,
> > > but (again, last I knew) it was never submitted
> > > upstream (it was reported some of the code
> > > included non-GPL copyright, and I presume
> > > it could not be re-licensed).
> > 
> > Yes, that's the driver I'm using.
> > ___
> > pvrusb2 mailing list
> > pvrusb2@isely.net
> > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> > 
> 
> 

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-17 Thread isely 

Ian:

Wait a second.  Now I'm confused.  Are you or are not using the pvrusb2 
driver?  The error you quoted was definitely phrasing that would have 
come from the pvrusb2 driver.  If you're using something else entirely 
different I'd be VERY curious know why the resemblence.

Also - to others here - I'm confused about something else.  This sounds 
like we're talking about 3 drivers:

1. The pvrusb2 driver, in the kernel mainline.

2. Something on the Hauppauge web site, apparently freely accessible.

3. Something from Hauppauge that can't be acquired without an NDA.

Is this correct?  Anyone, chime in.

  -Mike


On Mon, 12 Sep 2016, Ian Goldberg wrote:

> On Tue, Sep 13, 2016 at 12:37:25AM +, Gary Buhrmaster wrote:
> > On Mon, Sep 12, 2016 at 10:35 PM,   wrote:
> > 
> > > I know basically nothing about the HVR-1975.
> > 
> > As I understand it, the HVR-1975 is essentially
> > a "one size fits all" redesign of the basic HVR-1900
> > and the HVR-1950/1955 which is compatible with
> > both US and DVB standards [mostly for commercial
> > embedded solutions that want one SKU for either
> > location (it actually contains two demods)].
> > 
> > Hauppuage (last I knew) reportedly offered an out
> > of tree driver on their website for the HVR-1975,
> > but (again, last I knew) it was never submitted
> > upstream (it was reported some of the code
> > included non-GPL copyright, and I presume
> > it could not be re-licensed).
> 
> Yes, that's the driver I'm using.
> ___
> pvrusb2 mailing list
> pvrusb2@isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> 

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Ian Goldberg 
On Mon, Sep 12, 2016 at 08:45:19PM -0400, Roger wrote:
> kernel 3.16
> http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz
> 
> kernel 3.19 patch
> http://hauppauge.lightpath.net/software/linux/hvr-9x5-19x5-22x5-kernel-3.19-2015-07-10-v2.patch.tar.xz
> 
> kernel 4.2 (already has) built in support for the WinTV-HVR-955Q.
> 
> At this point, I'm wondering if the drivers also for the HVR-1955/1975 are 
> included within kernel >= 4.2?
> 
> 
> Interesting, does the original poster have access to the Internet, or to 
> hauppauge.com?

Yes, as I said, those are in fact the drivers I'm using (the 3.16
version).  Kernel 4.2+ has drivers in it for the 1950, but not the 1975.

   - Ian
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Roger 

2014.02.26 Hauppauge Press release:
http://www.hauppauge.com/pdfs/pr_hauppauge_wintv-hvr-1975.pdf
"We expect the WinTV-HVR-1975 to be used in Linux based systems for digital 
signage, sports equipment, hospital patient entertainment systems and other TV 
watching and high speed data delivery applications"

"For Linux system builders, Hauppauge has driver support which can be provided 
under NDA."

LinuxTV.org Hauppauge WinTV-HVR-1950
https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1950
Note: As of August 2014, the WinTV-HVR-1955 is sometimes shipped instead of the 
HVR-1950. The HVR-1955 does not, at this time, have a open-source driver 
available.  A source-level driver for Linux is available from Hauppauge after a 
NDA is signed. Hauppauge technical support can be contacted for more details.

>From the above, I'm ascertaining the HVR-1955 is possibly the HVR-1975, or 
similar situation.  Judging by the press release, I'm guessing contacting 
Hauppauge will result in the firmwares being released after a NDA is signed.

I'll take a gander, likely one or two chips (or maybe some of the code for the 
firmware) have questionable disclosures attached during the 
engineering/manufacturing process.  And may or may not be provided openly at a 
later date.  But then I stumble back on this thought, and if it's just the 
firmwares, we should be able to extract them from the Windows' driver package.

Take a further look at a mailing list post by dheitmueller at kernellabs on Mar 
7, 2016, 7:39 AM (Post #9 of 15)
http://www.gossamer-threads.com/lists/mythtv/users/597124

I think dheitmueller did a good job explaining some of the material.

(I prefer to copy the material here, but think I've wrote enough already.)

Of course that list ends up recently asking this list for further information!  

But as dheitmueller stated within his post, or somebody immediately following 
his post, the Linux HVR-1955/1975 drivers are posted on this page.
http://www.hauppauge.com/site/support/linux.html

kernel 3.16
http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz

kernel 3.19 patch
http://hauppauge.lightpath.net/software/linux/hvr-9x5-19x5-22x5-kernel-3.19-2015-07-10-v2.patch.tar.xz

kernel 4.2 (already has) built in support for the WinTV-HVR-955Q.

At this point, I'm wondering if the drivers also for the HVR-1955/1975 are 
included within kernel >= 4.2?


Interesting, does the original poster have access to the Internet, or to 
hauppauge.com?


> On Mon, Sep 12, 2016 at 05:35:17PM -0500, is...@isely.net wrote:
> (snip)
>I know basically nothing about the HVR-1975.  Again sorry, been out of this 
>too long.  Is it even compatible?  (If you bought the '1950 but got this then 
>it's probably reasonably close.)  Has anyone else successfully used this 
>model?  Frankly I figured after all this time and with the world moving to 
>digital video streams that this technology from 2003 would be fading away...  
>But as I said, I've been away too long and am not up to speed.
>
>  -Mike

Off-topic, most digital streams (including satellite subscription TV) are 
compressed video & audio.  Your over-the-air broadcast TV is of slightly better 
quality and it's free.  One just needs to know how to install an antenna, 
cabling, etc...  I've even experience broadcast TV having superior quality 
audio versus Cable TV, but that was a few years ago.

-- 
Roger
http://rogerx.freeshell.org/
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Ian Goldberg 
On Tue, Sep 13, 2016 at 12:37:25AM +, Gary Buhrmaster wrote:
> On Mon, Sep 12, 2016 at 10:35 PM,   wrote:
> 
> > I know basically nothing about the HVR-1975.
> 
> As I understand it, the HVR-1975 is essentially
> a "one size fits all" redesign of the basic HVR-1900
> and the HVR-1950/1955 which is compatible with
> both US and DVB standards [mostly for commercial
> embedded solutions that want one SKU for either
> location (it actually contains two demods)].
> 
> Hauppuage (last I knew) reportedly offered an out
> of tree driver on their website for the HVR-1975,
> but (again, last I knew) it was never submitted
> upstream (it was reported some of the code
> included non-GPL copyright, and I presume
> it could not be re-licensed).

Yes, that's the driver I'm using.
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Gary Buhrmaster 
On Mon, Sep 12, 2016 at 10:35 PM,   wrote:

> I know basically nothing about the HVR-1975.

As I understand it, the HVR-1975 is essentially
a "one size fits all" redesign of the basic HVR-1900
and the HVR-1950/1955 which is compatible with
both US and DVB standards [mostly for commercial
embedded solutions that want one SKU for either
location (it actually contains two demods)].

Hauppuage (last I knew) reportedly offered an out
of tree driver on their website for the HVR-1975,
but (again, last I knew) it was never submitted
upstream (it was reported some of the code
included non-GPL copyright, and I presume
it could not be re-licensed).
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread isely 

The driver is getting upset because it can't load "firmware2", which is 
the firmware needed for the mpeg2 encoder IC in the device.  Without 
that firmware, the encoder can't run and basically you won't be able to 
get any mpeg data at all from the device.

Looking at the function in question, it appears that the pvrusb2 driver 
did in fact locate the expected firmware file name and that the firmware 
file passed basic sanity (size must be multiple of 4 bytes).  However, 
after sending the image, the mpeg encoder refused to wake up and start 
running, thus the failure.  It's possible that either the mpeg2 encoder 
firmware image for an HVR-1975 is different than other models (which 
would be a first), or that the firmware image file installed on your 
system (part of that patch?  I really don't know) is corrupted.

I know basically nothing about the HVR-1975.  Again sorry, been out of 
this too long.  Is it even compatible?  (If you bought the '1950 but got 
this then it's probably reasonably close.)  Has anyone else successfully 
used this model?  Frankly I figured after all this time and with the 
world moving to digital video streams that this technology from 2003 
would be fading away...  But as I said, I've been away too long and am 
not up to speed.

  -Mike



On Mon, 12 Sep 2016, Ian Goldberg wrote:

> Hi, all.
> 
> I recently purchased two Hauppauge WinTV HVR-1975 devices (well, I
> purchased 1950s, but you know how it is), for use with my MythTV box.
> 
> The machine is running Mythbuntu 14.04, and I downloaded
> linux-lts-utopic_3.16.0-77.99~14.04.1 and applied the patch
> http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz
> (and it applied perfectly cleanly).
> 
> I've booted into that kernel, and *some* bits work, but video doesn't.
> There's an lirc0 device, and I can control the computer using the
> Hauppauge remote, so that's good.  There are video0 and video1 devices,
> but if I do "cat /dev/video0", I get in kern.log:
> 
> Sep 12 17:52:04 brennan kernel: [84445.104528] pvrusb2: Clearing driver error 
> statuss
> Sep 12 17:52:04 brennan kernel: [84445.569299] pvrusb2: firmware2 upload 
> transfer failure
> Sep 12 17:52:04 brennan kernel: [84445.570010] pvrusb2: Clearing driver error 
> statuss
> Sep 12 17:52:05 brennan kernel: [84446.037511] pvrusb2: firmware2 upload 
> transfer failure
> 
> (Oddly, I just noticed that if I do "cat /dev/video1", I get in
> kern.log:
> 
> Sep 12 17:51:39 brennan kernel: [84420.310628] cx25840 8-0044: loaded 
> v4l-cx25840.fw firmware (16382 bytes)
> Sep 12 17:51:39 brennan kernel: [84420.389304] 
> silabs_tercab_set_analog_params: [8-0060] using video_sys 
> Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
> Sep 12 17:51:39 brennan kernel: [84420.389663] 
> silabs_tercab_set_analog_params: [8-0060] silabs_tercab_set_analog_params(): 
> initializing tuner type Si2177
> Sep 12 17:51:40 brennan kernel: [84420.763169] 
> silabs_tercab_set_analog_params: [8-0060] using video_sys 
> Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
> Sep 12 17:51:40 brennan kernel: [84420.763578] 
> silabs_tercab_set_analog_params: [8-0060] silabs_tercab_set_analog_params(): 
> initializing tuner type Si2177
> Sep 12 17:51:40 brennan kernel: [84421.122188] 
> silabs_tercab_set_analog_params: [8-0060] using video_sys 
> Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
> Sep 12 17:51:40 brennan kernel: [84421.122540] 
> silabs_tercab_set_analog_params: [8-0060] silabs_tercab_set_analog_params(): 
> initializing tuner type Si2177
> 
> and then a bunch of data actually does come out, but it's just an mpg of
> snow.  Maybe the proper input isn't selected?)
> 
> There's also no /dev/lirc1, and when I try to irsend to /dev/lirc0,
> lircd throws an error.  The strace is:
> 
> ioctl(7, IPMICTL_SET_MY_LUN_CMD or LIRC_SET_SEND_CARRIER, 0x7ffe88ab4a1c) = 0
> write(7, "\5\0N\0", 4)  = -1 EINVAL (Invalid argument)
> 
> so I can't use the blasters for some reason.
> 
> Any thoughts about the firmware upload failure and the lack of blasting
> ability?
> 
> The kernel log when attaching a device is below.
> 
> Thanks,
> 
>- Ian
> 
> 
> 
> 
> Sep 12 17:42:38 brennan kernel: [83878.440917] usb 2-4: new high-speed USB 
> device number 15 using xhci_hcd
> Sep 12 17:42:38 brennan kernel: [83878.573024] usb 2-4: New USB device found, 
> idVendor=2040, idProduct=7510
> Sep 12 17:42:38 brennan kernel: [83878.573031] usb 2-4: New USB device 
> strings: Mfr=1, Product=2, SerialNumber=3
> Sep 12 17:42:38 brennan kernel: [83878.573035] usb 2-4: Product: WinTV
> Sep 12 17:42:38 brennan kernel: [83878.573038] usb 2-4: Manufacturer: 
> Hauppauge
> Sep 12 17:42:38 brennan kernel: [83878.573041] usb 2-4: SerialNumber: 
> 7300-00-F08E07DC
> Sep 12 17:42:38 brennan kernel: [83878.573647] pvrusb2: Hardware description: 
> WinTV HVR-1975 Model 16
> Sep 12 17:42:39 brennan kernel: [83879.575404] pvrusb2: Device 
> microcontroller firmware (re)loaded; it should now reset and reconnect.
> Sep 12