Re: Hauppauge WinTV-HVR2205 driver feedback

Op 11-10-15 om 08:18 schreef Richard Tresidder: Hi Again Yep that fixed pulling in the saa7164: si2168 frontends: [ 6778.591548] i2c i2c-15: Added multiplexed i2c bus 16 [ 6778.591556] si2168 15-0064: Silicon Labs Si2168 successfully attached [ 6778.596252] si2157 13-0060: Silicon Labs

Re: Hauppauge WinTV-HVR2205 driver feedback

Hi Again Yep that fixed pulling in the saa7164: si2168 frontends: [ 6778.591548] i2c i2c-15: Added multiplexed i2c bus 16 [ 6778.591556] si2168 15-0064: Silicon Labs Si2168 successfully attached [ 6778.596252] si2157 13-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached [

Re: Hauppauge WinTV-HVR2205 driver feedback

Hi, not sure if this is related. I had to recompile the centos7 stock kernel with: CONFIG_I2C_MUX=m It was not enabled in the kernel config. Op 04-10-15 om 06:55 schreef Richard Tresidder: Sorry If I've posted this to the wrong section my first attempt.. Hi I'm attempting to get an HVR2205

Re: Hauppauge WinTV-HVR2205 driver feedback

On 05/10/15 22:22, Steven Toth wrote: On Sun, Oct 4, 2015 at 9:59 PM, Richard Tresidder wrote: Hi Steven Nope standard x86_64 kernel 3.10.0-229.14.1.el7.x86_64 Hmm. Was rather surprised as all my quick reading indicates that the kernel should quite

Re: Hauppauge WinTV-HVR2205 driver feedback

Hmm indeed... I see that the 2168 wants a mux i2c adapter.. and yep my /boot/config-3.10.0-229.14.1.el7.x86_64/ is indeed showing that CONFIG_I2C_MUX is commented out.. sigh.. Rebuilding the kernel with that setting on... Why this is disabled rather than just a module is beyond me.. Curious

Re: Hauppauge WinTV-HVR2205 driver feedback

On Sun, Oct 4, 2015 at 9:59 PM, Richard Tresidder wrote: > Hi Steven >Nope standard x86_64 > kernel 3.10.0-229.14.1.el7.x86_64 Hmm. > > Was rather surprised as all my quick reading indicates that the kernel > should quite happily do this... > Though looks

Re: Hauppauge WinTV-HVR2205 driver feedback

>> Do you have a large number of other devices / drivers loaded? I >> suspect another driver is burning through kernel memory before the >> saa7164 has a chance to be initialized. > > Nope nothing I can see Its actually the only addon card I have in this > system.. > I'd be buggered If 4GB of RAM

Re: Hauppauge WinTV-HVR2205 driver feedback

Hi Just for clarification I forgot to add that I had already got past that little bump by chunking the allocation to src_buf in the same loop as the memcpy_toio But I'll rebuild the module with the memcpy_toio directly accessing src and see how it goes. Regards Richard Tresidder On

Re: Hauppauge WinTV-HVR2205 driver feedback

stage 1.. Yep it works with accessing src directly.. had to reboot to verify that one. Well at least the download says it worked and the image booted successfully. excuse my manual diff method.. git and I don't agree... not sure how to get it to diff the media_build repo I pulled the code

Re: Hauppauge WinTV-HVR2205 driver feedback

On Mon, Oct 5, 2015 at 11:26 AM, Richard Tresidder wrote: > stage 1.. > Yep it works with accessing src directly.. had to reboot to verify that one. > Well at least the download says it worked and the image booted successfully. > > excuse my manual diff

Re: Hauppauge WinTV-HVR2205 driver feedback

Sigh again Did a module only build for the i2c-mux and got it into the currently running kernel with a force to bypass the no symbol version for module_layout error.. figured it was safe enough given it was the identical kernel config etc from the centos vault... Anyway still failed..

Re: Hauppauge WinTV-HVR2205 driver feedback

Hi Steven Nope standard x86_64 kernel 3.10.0-229.14.1.el7.x86_64 Was rather surprised as all my quick reading indicates that the kernel should quite happily do this... Though looks like its the largest chunk you can request? I'm not well enough up to speed with the nitty gritty.. There is

Re: Hauppauge WinTV-HVR2205 driver feedback

> Seems the kzalloc(4 * 1048576, GFP_KERNEL) in saa7164-fw.c was failing.. > kept getting: kernel: modprobe: page allocation failure: order:10, > mode:0x10c0d0 I don't think I've ever seen or heard of that in the entire history of the driver. Are you running on traditional x86/x86 hardware, or

Re: Hauppauge WinTV-HVR2205 driver feedback

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

Re: Hauppauge WinTV-HVR2205 driver feedback

My card has been always installed in a machine that does not have Windows, so any interference with the Windows driver should not be an issue. I found some old console logs from February 21 when I was trying to put together a driver for the board. It shows that the Si2168 chip on my board was at

Re: Hauppauge WinTV-HVR2205 driver feedback

If the GPIOs aren't truly resetting the SI2168 and thus a warm boot didn't flush the firmware, I suspect dropping the patches would have no immediate effect until a full power-down took place. I'm wondering whether the testing was invalid and indeed we have a problem in the field, as well as

Re: Hauppauge WinTV-HVR2205 driver feedback

On 06/03/2015 10:08 PM, Olli Salonen wrote: I cold booted my number cruncher after a hiatus of a couple of weeks, applied a couple of extra dev_dbg printouts in the si2168_cmd_execute and installed the newly built module. The results: [ 663.147757] si2168 2-0066: Silicon Labs Si2168

Re: Hauppauge WinTV-HVR2205 driver feedback

I cold booted my number cruncher after a hiatus of a couple of weeks, applied a couple of extra dev_dbg printouts in the si2168_cmd_execute and installed the newly built module. The results: [ 663.147757] si2168 2-0066: Silicon Labs Si2168 successfully attached [ 663.151735] si2157 1-0060:

Re: Hauppauge WinTV-HVR2205 driver feedback

I have a working solution (workaround) for the HVR2205/HVR2215 firmware loading issue. In the file: dvb-frontends/si2168.c change: #define SI2168_B40 ('B' 24 | 68 16 | '4' 8 | '0' 0) to: #define SI2168_B40 (68 16 | '4' 8 | '0' 0) I do not know why this works, but this is

Re: Hauppauge WinTV-HVR2205 driver feedback

Steven Toth stoth at kernellabs.com writes: Many thanks to the developers for all of your hard work. Let me guess they have changed Si2168 chip to latest C version. Driver supports only A and B (A20, A30 and B40). I have never seen C version. I'll look in detail and report back

RE: Hauppauge WinTV-HVR2205 driver feedback

] si2168 22-0064: unknown chip version Si2168- [170762.907071] si2168 22-0064: unknown chip version Si2168- -Original Message- From: Antti Palosaari [mailto:cr...@iki.fi] Sent: Wednesday, June 3, 2015 6:03 PM To: Stephen Allan; linux-media@vger.kernel.org Subject: Re: Hauppauge WinTV

Re: Hauppauge WinTV-HVR2205 driver feedback

On 06/03/2015 06:55 AM, Stephen Allan wrote: I am aware that there is some development going on for the saa7164 driver to support the Hauppauge WinTV-HVR2205. I thought I would post some feedback. I have recently compiled the driver as at 2015-05-31 using media build tree. I am unable to

Re: Hauppauge WinTV-HVR2205 driver feedback

On 06/03/2015 10:55 AM, Antti Palosaari wrote: On 06/03/2015 06:55 AM, Stephen Allan wrote: I am aware that there is some development going on for the saa7164 driver to support the Hauppauge WinTV-HVR2205. I thought I would post some feedback. I have recently compiled the driver as at

Re: Hauppauge WinTV-HVR2205 driver feedback

I'm seeing the same issue as well. I thought that maybe some recent Si2168 changes did impact this, but it does not seem to be the case. I made a quick test myself. I reverted the latest si2168 patches one by one, but that did not remedy the situation. Anyway, the kernel log does not seem to

Re: Hauppauge WinTV-HVR2205 driver feedback

Many thanks to the developers for all of your hard work. Let me guess they have changed Si2168 chip to latest C version. Driver supports only A and B (A20, A30 and B40). I have never seen C version. I'll look in detail and report back shortly. -- Steven Toth - Kernel Labs

Re: Hauppauge WinTV-HVR2205 driver feedback

On Wed, Jun 3, 2015 at 5:29 AM, Olli Salonen olli.salo...@iki.fi wrote: I'm seeing the same issue as well. I thought that maybe some recent Si2168 changes did impact this, but it does not seem to be the case. We've had a couple of people raise this so its highly likely we have an issue. I had

Re: Hauppauge WinTV-HVR2205 driver feedback

On 06/03/2015 12:29 PM, Olli Salonen wrote: I'm seeing the same issue as well. I thought that maybe some recent Si2168 changes did impact this, but it does not seem to be the case. I made a quick test myself. I reverted the latest si2168 patches one by one, but that did not remedy the

RE: Hauppauge WinTV-HVR2205 driver feedback

-media@vger.kernel.org Subject: Re: Hauppauge WinTV-HVR2205 driver feedback On 06/03/2015 10:55 AM, Antti Palosaari wrote: On 06/03/2015 06:55 AM, Stephen Allan wrote: I am aware that there is some development going on for the saa7164 driver to support the Hauppauge WinTV-HVR2205. I thought I would