From: emagick@magic.ms
To: linux-media@vger.kernel.org
Subject: Re: Cinergy T2 stopped working with kernel 2.6.30
Date: Thu, 30 Jul 2009 11:49:10 +0200 [thread overview]
Message-ID: <4A716C96.1080404@magic.ms> (raw)
In-Reply-To: <4A61FD76.8010409@magic.ms>
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 cannot tune
CONFIG_MCORE2 | cannot tune cannot tune
These results are for my Atom N270 board. On my Core2 board, the Cinergy T2 works
all the time.
By applying -march=i486 and -march=i586 to individual source files, I found
out that dvb_frontend.c is the culprit.
By editing the assembly output for dvb_frontend.c, I found out that only
dvb_frontend_swzigzag_autotune() needs to be compiled with CONFIG_M486 to
make the Cinergy T2 work, everything else can be compiled with CONFIG_M586.
Both compiled versions of dvb_frontend_swzigzag_autotune() look OK (but I
haven't yet strictly verified the assembly code). Anyway, nothing in that
code should make a difference on N270 vs. Core, except for timing. Adding
NOPs doesn't seem to make a difference.
Any ideas? Could this be a CPU bug?
next prev parent reply other threads:[~2009-07-30 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 16:51 Cinergy T2 stopped working with kernel 2.6.30 emagick
2009-07-23 8:20 ` emagick
2009-07-30 9:49 ` emagick [this message]
2009-07-30 17:46 ` emagick
2009-07-31 8:39 ` emagick
2009-07-31 8:43 ` emagick
2009-07-31 8:48 ` emagick
2009-07-31 18:44 ` emagick
2009-07-31 19:37 ` emagick
2009-07-31 19:47 ` emagick
2009-07-31 19:50 ` Markus Rechberger
2009-07-31 21:31 ` Johannes Stezenbach
2009-08-02 7:43 ` [PATCH] dvb-usb: fix tuning with Cinergy T2 emagick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A716C96.1080404@magic.ms \
--to=emagick@magic.ms \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.