Re: Cinergy T2 stopped working with kernel 2.6.30

2009-07-31 Thread Johannes Stezenbach
On Fri, Jul 31, 2009 at 08:44:59PM +0200, emag...@magic.ms wrote: > > static int cinergyt2_fe_set_frontend(struct dvb_frontend *fe, > struct dvb_frontend_parameters *fep) > { > struct cine

Re: Cinergy T2 stopped working with kernel 2.6.30

2009-07-31 Thread Markus Rechberger
On Fri, Jul 31, 2009 at 9:47 PM, wrote: > Apparently, usb_bulk_msg() cannot be used with data on the stack: > > http://www.linuxtv.org/pipermail/linux-dvb/2008-August/028150.html > http://www.mail-archive.com/linux-usb-de...@lists.sourceforge.net/msg19158.html > -- As far as I recall this has bee

Re: Cinergy T2 stopped working with kernel 2.6.30

2009-07-31 Thread emagick
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 = fe->demodulato

Re: Cinergy T2 stopped working with kernel 2.6.30

2009-07-31 Thread emagick
I wrote: Addendum: with 3 additional local variables and compiled for i486 mythweb fails to tune, but mplayer can tune. Note that I mentioned cases where mplayer can tune but mythweb fails to tune. Perhaps alignment in the user-mode stack is a factor. Oops, there was no instance of mythweb b

Re: Cinergy T2 stopped working with kernel 2.6.30

2009-07-31 Thread emagick
Addendum: with 3 additional local variables and compiled for i486 mythweb fails to tune, but mplayer can tune. Note that I mentioned cases where mplayer can tune but mythweb fails to tune. Perhaps alignment in the user-mode stack is a factor. Anyone listening? -- To unsubscribe from this list:

Re: Cinergy T2 stopped working with kernel 2.6.30

2009-07-31 Thread emagick
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 failu

Re: Cinergy T2 stopped working with kernel 2.6.30

2009-07-30 Thread emagick
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

2009-07-30 Thread emagick
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

2009-07-23 Thread emagick
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 60db56422043aaa455ac7f858

Cinergy T2 stopped working with kernel 2.6.30

2009-07-18 Thread emagick
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 cha