Ken,
You could set the module parameter preallocate_big_buffers=1 when
you insmod the au8028 kernel module. When this parameter is set, the
driver will allocate the big buffers once when the module is loaded
instead of every time the device is opened for streaming.
Thanks,
Tim
On Fri, Oc
On Wed, Jan 8, 2014 at 1:26 PM, Devin Heitmueller
wrote:
> Hi Tim,
>
> On Wed, Jan 8, 2014 at 12:12 AM, Tim Mester wrote:
>> Commit 2e68a75990011ccd looks interesting. It makes sense to me
>> that if we are gating the clock, and it is possible that we are
>> glitchi
On Mon, Jan 6, 2014 at 9:53 PM, Devin Heitmueller
wrote:
>> I suspect this is actually a different problem which out of dumb luck
>> gets "fixed" by resetting the chip. Without more details on the
>> specific behavior you are seeing though I cannot really advise on what
>> the correct change is.
On Mon, Jan 6, 2014 at 9:45 PM, Devin Heitmueller
wrote:
>
> On Mon, Jan 6, 2014 at 11:29 PM, Tim Mester wrote:
> > The demodulator can get in a state in ATSC mode where just
> > restarting the feed alone does not correct the corrupted stream. The
> > demodulator reset
Added command line parameter preallocate_big_buffers so that the digital
transfer buffers can be allocated when the driver is registered. They
do not have to be allocated every time a feed is started.
Signed-off-by: Tim Mester
---
linux/drivers/media/usb/au0828/au0828-core.c | 13
same frequency and modulation mode, the demodulator
will be reset. The au0282 drives uses this feature when it attempts
to restart the feed.
Signed-off-by: Tim Mester
---
linux/drivers/media/dvb-frontends/au8522_dig.c | 38 +-
linux/drivers/media/usb/au0828/au0828-dvb.c
: Tim Mester
---
linux/drivers/media/usb/au0828/au0828-dvb.c | 70 +
linux/drivers/media/usb/au0828/au0828.h | 2 +
2 files changed, 53 insertions(+), 19 deletions(-)
diff --git a/linux/drivers/media/usb/au0828/au0828-dvb.c
b/linux/drivers/media/usb/au0828/au0828
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 0x2
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