1) The comments above the 44.1Khz and 48Khz SET_SRC4 and SET_SRC6 blocks aren't what the code is doing (they look like they are cut and paste from the 32Khz but not updated to reflect the changes in the phase_inc. No need for a patch here unless you want me to generate one:
+++ cx25840-driver.c (working copy)
- // src4_ctl = 0x0801f77f;
+ // src4_ctl = 0x08016d59;
- // src6_ctl = 0x0801f77f;
+ // src6_ctl = 0x08016d59;
- // src4_ctl = 0x0801f77f;
+ // src4_ctl = 0x08014faa;
- // src6_ctl = 0x0801f77f;
+ // src6_ctl = 0x0801ffaa;
2) In the hauppauge driver's line in sample rate setup, a full 4 bytes is written to set up SRC1. In our code we only write the 3 bytes of the PHASE_INC. If you look at the comment above our line, it looks like it means to set 4 bytes as well:
// src1_ctl = 0x08010000;
CX25840_SET_SRC1_PHASE_INC(0x10000);
Problem is that we don't have a CX25840_SET_SRC1_FIFO_RD_TH setting defined where we can put that 0x08. How is cx25840-registers.c automatically generated? I doubt this is important, but it is an area where the linux driver differs from its windows sibling. If the SRC1_FIFO_RD_TH setting is added, all 3 line-in
samplerates should have a CX25840_SET_SRC1_FIFO_RD_TH(0x08) appended to match the setup done in windows.
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
