On Sun, Nov 1, 2009 at 7:37 AM, Andy Walls <awalls@xxxxxxxxx> wrote: > On Sat, 2009-10-31 at 22:25 -0400, Brandon Jenkins wrote: >> On Sat, Oct 31, 2009 at 8:41 PM, Andy Walls <awalls@xxxxxxxxx> wrote: >> > On Sat, 2009-10-31 at 16:28 -0400, Devin Heitmueller wrote: >> >> On Sat, Oct 31, 2009 at 4:16 PM, Andy Walls <awalls@xxxxxxxxx> wrote: >> > >> >> >> >> Hi Andy, >> >> >> >> How does this code work if the cx23418 scaler is used (resulting in >> >> the size of the frames to be non-constant)? Or is the scaler not >> >> currently supported in the driver? >> > >> > I also forgot to mention, changing size while the encoder has an analog >> > stream running (MPEG, VBI, YUV, IDX) is not permitted by the firmware. >> > So this change works just fine as it computes the buffer size to use >> > just as it sets up to start the capture. >> > >> > Regards, >> > Andy > >> Hi Andy, > > Hi Brandon, > >> I tried to pull your changes and received an error on a missing .hg. > > Sorry, I can't help there. The following should work: > > hg clone http://linuxtv.org/hg/~awalls/cx18-yuv > > >> Subsequently, I downloaded the bz2 file and upon reboot I received a >> kernel panic due to DMA issues. > > Did it fail on MPEG or Digital TS captures or on a YUV capture? > > Did you try setting enc_yuv_bufs=0, to inhibit YUV buffer allocation, to > see if the panic went away? > > Could you provide the panic to me? Off-list is fine. > > If I can't get this large buffer scheme to work for the general case to > mainatin YUV frame alignment, I'll have to figure out what will likely > be a much more complex scheme to ensure alignment is maintained in for > YUV streams. :( > > Oh, well. > > Regards, > Andy > > > Hi Andy, The panic happens upon reboot and it is only 1 line of text oddly shifted. Kernel panic - not syncing: DMA: Memory would be corrupted If I switch back to the current v4l-dvb drivers no issue. To switch back I have to boot from a USB drive. Brandon -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
