From: Gerd Knorr <kraxel@bytesex.org>
To: "Subbu K. K." <kksubramaniam@novell.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Fix for "MT2032 Fatal Error: PLLs didn't lock"
Date: Tue, 25 Nov 2003 09:50:56 +0100 [thread overview]
Message-ID: <20031125085056.GA5440@bytesex.org> (raw)
In-Reply-To: <1069743507.1270.2.camel@dog.blr.novell.com>
> Except in one place where there is an implicit conversion to signed ints
> in line 746:
>
> 746 mt2032_set_if_freq(c, freq*62500 /* freq*1000*1000/16 */,
Sure? Both freq and second mt2032_set_if_freq argument are declared
unsigned int ...
What happens with "62500" changed to "(unsigned)62500" ?
> > tuner: tv freq set to 140.25
> > mt2032_set_if_freq rfin=140250000 if1=1090000000 if2=38900000 from=32900000 to=39900000
> Thanks for the clue. Perhaps the problem is gcc/athlon related?
Maybe. gcc 3.3.1 here.
Gerd
--
You have a new virus in /var/mail/kraxel
next prev parent reply other threads:[~2003-11-25 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031124004835.3abbb4cf.akpm@osdl.org>
2003-11-24 11:46 ` Fix for "MT2032 Fatal Error: PLLs didn't lock" Gerd Knorr
2003-11-25 6:58 ` Subbu K. K.
2003-11-25 8:50 ` Gerd Knorr [this message]
2003-11-27 7:26 ` Subbu K. K.
2003-11-24 8:01 Subbu K. K.
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=20031125085056.GA5440@bytesex.org \
--to=kraxel@bytesex.org \
--cc=akpm@osdl.org \
--cc=kksubramaniam@novell.com \
--cc=linux-kernel@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.