linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Tresidder <rtresidd@tresar-electronics.com.au>
To: linux-media@vger.kernel.org
Subject: Re: Hauppauge WinTV-HVR2205 driver feedback
Date: Sun, 4 Oct 2015 12:55:07 +0800	[thread overview]
Message-ID: <5610B12B.8090201@tresar-electronics.com.au> (raw)

Sorry If I've posted this to the wrong section my first attempt..

Hi
    I'm attempting to get an HVR2205 up and going.
CORE saa7164[1]: subsystem: 0070:f120, board: Hauppauge WinTV-HVR2205 
[card=13,autodetected]
Distribution is CentOS7 so I've pulled the v4l from media_build.git
Had to change a couple of things..  and another macro issue regarding 
clamp() ..
Seems the kzalloc(4 * 1048576, GFP_KERNEL) in saa7164-fw.c  was failing..
kept getting:  kernel: modprobe: page allocation failure: order:10, 
mode:0x10c0d0
Have plenty of RAM free so surprised about that one.. tried some of the 
tricks re increasing the vm.min_free_kbytes etc..

Any way I modified the routine to only allocate a single chunk buffer 
based on dstsize and tweaked the chunk handling code..
seemed to fix that one.. fw downloaded and seemed to boot ok..

Next I'm running into a problem with the saa7164_dvb_register() stage...

saa7164[1]: Hauppauge eeprom: model=151609
saa7164_dvb_register() Frontend/I2C initialization failed
saa7164_initdev() Failed to register dvb adapters on porta

I added some extra debug and identified that client_demod->dev.driver is 
null..

However I'm now stuck as to what to tackle next..

I can provide more info, just didn't want to spam the list for my first 
email..

Regards
    Richard Tresidder

             reply	other threads:[~2015-10-04  5:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04  4:55 Richard Tresidder [this message]
2015-10-04 14:03 ` Hauppauge WinTV-HVR2205 driver feedback Steven Toth
2015-10-05  1:59   ` Richard Tresidder
2015-10-05 14:22     ` Steven Toth
2015-10-05 14:35       ` Richard Tresidder
2015-10-05 14:39         ` Richard Tresidder
2015-10-05 14:43         ` Steven Toth
2015-10-05 15:26           ` Richard Tresidder
2015-10-05 15:32             ` Steven Toth
2015-10-05 12:45 ` Tycho Lürsen
2015-10-05 14:22   ` Richard Tresidder
2015-10-05 16:03   ` Richard Tresidder
2015-10-11  6:18   ` Richard Tresidder
2015-10-11  7:33     ` Tycho Lürsen
  -- strict thread matches above, loose matches on Subject: below --
2015-06-03  3:55 Stephen Allan
2015-06-03  7:55 ` Antti Palosaari
2015-06-03  8:02   ` Antti Palosaari
2015-06-03  9:29     ` Olli Salonen
2015-06-03 14:30       ` Steven Toth
2015-06-04 12:46         ` Steven Toth
2015-06-03 15:34       ` Antti Palosaari
2015-06-03 19:08         ` Olli Salonen
2015-06-03 19:46           ` Antti Palosaari
2015-06-04  8:07             ` Olli Salonen
2015-06-04  0:38     ` Stephen Allan
2015-06-04  1:22       ` faulkner-ball
2015-06-03 14:31   ` Steven Toth
2015-06-03 21:50     ` Peter Faulkner-Ball
2015-06-03 22:16       ` 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=5610B12B.8090201@tresar-electronics.com.au \
    --to=rtresidd@tresar-electronics.com.au \
    --cc=linux-media@vger.kernel.org \
    /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).