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
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 =
On Fri, Jul 31, 2009 at 9:47 PM, emag...@magic.ms 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
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
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
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
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
