I have updated the patch from http://www.linuxtv.org/pipermail/linux-dvb/2008-December/030786.html
to add QAM64 support to the HVR-950Q. It is working well for me.
What needs to happen to get this included in v4l-dvb?
Thanks,
Britney
--- linux/drivers/media/dvb/frontends/au8522_dig.c.orig
On Thu, 2009-04-30 at 20:07 -0500, Britney Fransen wrote:
> I have updated the patch from
> http://www.linuxtv.org/pipermail/linux-dvb/2008-December/030786.html
> to add QAM64 support to the HVR-950Q. It is working well for me.
> What needs to happen to get this included in v4l-dvb?
Well,
I'm the original author of the patch. I included a "Signed-off-by:"
line when I submitted it (see the email Britney linked to). As far as
I can tell, the only modification to the patch is the file it is
applied to. This is exactly what I did after analog support was
merged, but I never submitted it
On Apr 30, 2009, at 8:55 PM, Frank Dischner wrote:
As far as
I can tell, the only modification to the patch is the file it is
applied to.
Frank, you are correct. The only change I made was to the new _dig.c
file that I believe changed with analog support. Do you want to
resubmit the patc
On Thu, Apr 30, 2009 at 10:17 PM, Britney Fransen
wrote:
> On Apr 30, 2009, at 8:55 PM, Frank Dischner wrote:
>
>> As far as
>> I can tell, the only modification to the patch is the file it is
>> applied to.
>
> Frank, you are correct. The only change I made was to the new _dig.c file
> that I be
On Thu, Apr 30, 2009 at 10:17 PM, Britney Fransen
wrote:
> On Apr 30, 2009, at 8:55 PM, Frank Dischner wrote:
>
>> As far as
>> I can tell, the only modification to the patch is the file it is
>> applied to.
>
> Frank, you are correct. The only change I made was to the new _dig.c file
> that I be
Here's the updated patch with the requested changes.
Frank
Signed-off-by: Frank Dischner
diff -urN v4l-dvb/linux/drivers/media/dvb/frontends/au8522_dig.c
v4l-dvb.new/linux/drivers/media/dvb/frontends/au8522_dig.c
--- v4l-dvb/linux/drivers/media/dvb/frontends/au8522_dig.c 2009-05-01
20:14:4
On Fri, May 1, 2009 at 11:17 PM, Frank Dischner
wrote:
> Here's the updated patch with the requested changes.
>
> Frank
Thanks,
Devin
--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the b
On Fri, May 1, 2009 at 11:17 PM, Frank Dischner
wrote:
> Here's the updated patch with the requested changes.
>
> Frank
Hello Frank,
Sorry for taking so long to get back to this.
I looked at the patch, and in particular, I compared the values
programmed for QAM256 against the table you provided
Hi Devin,
> Do you have the USB trace you used as the basis for this dump? And
> did you programatically parse that dump to generate the table, or did
> you enter it by hand? Could you please email me the underlying dump
> so I can double check the data?
I wrote a program to parse the trace and
On Mon, May 25, 2009 at 6:03 PM, Frank Dischner
wrote:
> While I'm at it, I thought I'd go ahead and make a patch to remove the
> top bits from the vsb table, but I've got a question about that. I
> think the first four entries are unnecessary. I'm pretty sure 8090 and
> 8091 have to do with the 8
On Mon, May 25, 2009 at 7:27 PM, Devin Heitmueller
wrote:
>
> On Mon, May 25, 2009 at 6:03 PM, Frank Dischner
> wrote:
> > While I'm at it, I thought I'd go ahead and make a patch to remove the
> > top bits from the vsb table, but I've got a question about that. I
> > think the first four entries
On Tue, May 26, 2009 at 2:35 PM, Tim Mester wrote:
> From my experience it seems that 2 in 0x2005 resets the 8522 demod.
> All demod register setting appear to be lost after accessing any
> registers in the 0x2xxx range (you really, just that bit needs to be
> set on a i2c bus access). I am a lit
On Tue, May 26, 2009 at 1:45 PM, Devin Heitmueller
wrote:
> On Tue, May 26, 2009 at 2:35 PM, Tim Mester wrote:
>> From my experience it seems that 2 in 0x2005 resets the 8522 demod.
>> All demod register setting appear to be lost after accessing any
>> registers in the 0x2xxx range (you really, j
14 matches
Mail list logo
