From: "John W. Linville" <linville@tuxdriver.com>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: 'Steven Blakeslee' <BlakesleeS@embeddedplanet.com>,
"'linuxppc-embedded@ozlabs.org'" <linuxppc-embedded@ozlabs.org>
Subject: Re: Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code
Date: Tue, 18 Jan 2005 15:29:15 -0500 [thread overview]
Message-ID: <20050118202913.GC6883@tuxdriver.com> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF0A647502@whq-msgusr-02.pit.comms.marconi.com>
On Tue, Jan 18, 2005 at 02:08:19PM -0500, Povolotsky, Alexander wrote:
> My board is using:
>
> bd->bi_intfreq = 50000000;
> bd->bi_busfreq = 50000000;
>
> While RPX-Lite is using
>
> bd->bi_intfreq = 48000000;
> bd->bi_busfreq = 48000000;
>
> Is this what makes RPX-Lite work and my (MPC 880) not ?
That, of course, depends on which value is correct for your
board... :-)
When I mentioned in one of our (possibly off-line) exchanges that
_slightly_ incorrect clock speeds might explain how you get a few good
characters from the serial port before you get all that garbage, this
is the kind of descrepancy I was suggesting. There may be enough
"slop" in the timings of the relatively slow serial port to make
48MHz and 50MHz "close enough" for a few characters.
So, what is the correct number for your board? Do you know how to
identify an oscillator? They have a bit of a 'tin can' look to them.
Find the one closest to the CPU on the board, and see what number is
on it.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-01-18 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 19:08 Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code Povolotsky, Alexander
2005-01-18 20:29 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 20:45 Povolotsky, Alexander
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=20050118202913.GC6883@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Alexander.Povolotsky@marconi.com \
--cc=BlakesleeS@embeddedplanet.com \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).