Re: Patch for stack/DMA problems in Cinergy T2 drivers (2)

Johannes Stezenbach wrote: There is a fair amount of code duplication. A better aproach would be to allocate buffers once in cinergyt2_fe_attach() (add them to struct cinergyt2_fe_state). Yes, but first I have to investigate why tuning is still quite unreliable (ie, more unreliable than in

Re: Patch for stack/DMA problems in Cinergy T2 drivers (2)

is not initialized to zero (as was done by kzalloc)! -emagick -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Patch for stack/DMA problems in Cinergy T2 drivers (2)

that the frontend ops are entered by only one thread at a time? -emagick -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Cinergy T2 stopped working with kernel 2.6.30

I've added dummy 32-bit variables to dvb_frontend_swzigzag_autotune() to change the frame size. Here are the results for mythweb (can tune/cannot tune): #variables i486 i586 0 ok failure 1 failureok 2 ok ok 3

Re: Cinergy T2 stopped working with kernel 2.6.30

I think I've found the problem: static int cinergyt2_fe_set_frontend(struct dvb_frontend *fe, struct dvb_frontend_parameters *fep) { struct cinergyt2_fe_state *state =

Patch for stack/DMA problems in Cinergy T2 drivers

There might be a more elegant solution, but this seems to work for me: --- drivers/media/dvb/dvb-usb/cinergyT2-fe.c2009-06-10 05:05:27.0 +0200 +++ drivers/media/dvb/dvb-usb/cinergyT2-fe.c2009-07-31 22:02:48.0 +0200 @@ -146,66 +146,103 @@

Re: Patch for stack/DMA problems in Cinergy T2 drivers

The patch I sent is incomplete, there are more instances of the same problem in cinergyT2-core.c. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Patch for stack/DMA problems in Cinergy T2 drivers (2)

Here's a patch for cinergyT2-core.c: --- a/drivers/media/dvb/dvb-usb/cinergyT2-fe.c 2009-06-10 05:05:27.0 +0200 +++ b/drivers/media/dvb/dvb-usb/cinergyT2-fe.c 2009-07-31 22:02:48.0 +0200 @@ -146,66 +146,103 @@ fe_status_t *status) {

Re: Cinergy T2 stopped working with kernel 2.6.30

The more I look into this problem the stranger it becomes. I've compiled the kernel for different CPUs: |mplayer mythtv -+ CONFIG_M486 |works works CONFIG_M586 |works

Re: Cinergy T2 stopped working with kernel 2.6.30

I've now compared the generated assembly code for dvb_frontend_swzigzag_autotune() built with CONFIG_M486 vs. CONFIG_M586. Both versions are correct, but the one compiled with -march=i586 (for which tuning does not work) uses more stack space (one 32-bit word). Does this ring any bells? -- To

Re: Cinergy T2 stopped working with kernel 2.6.30

There are two new discoveries about my Cinergy T2 problem: - the Cinergy T2 works when attached to an Intel Core2 board, but doesn't work when attached to an Intel Atom N270 board (tuning times out) - git bisect of the Linux kernel points to a bad merge of commit

Cinergy T2 stopped working with kernel 2.6.30

My Cinergy T2 (T²) doesn't work with kernels 2.6.30, 2.6.30.1, and 2.6.31-rc3, but it works with kernel 2.6.29. The kernel logs dvb-usb: recv bulk message failed: -110 and the application (I've tried mythtv and mplayer) trying to access the DVB receiver times out when trying to tune to a