From: Eugene Surovegin <ebs@ebshome.net>
To: Atit_Shah <Atit_Shah@Satyam.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Problem with linux porting
Date: Tue, 5 Apr 2005 03:01:27 -0700 [thread overview]
Message-ID: <20050405100126.GB29168@gate.ebshome.net> (raw)
In-Reply-To: <A44765C986F8D411995B00B0D0795F4B3A828130@hhtnt002>
On Tue, Apr 05, 2005 at 02:24:01PM +0530, Atit_Shah wrote:
> We are having a problem with porting of Linux.
[snip]
> 4. Frequency
>
> Core: 346MHz
>
> CPM: 198MHz
>
> BUS: 99MHz
>
> Input: 66MHz
What does "Input" clock mean?
If it's a CLKIN, why is Bus clock not equal to it?
--
Eugene
next prev parent reply other threads:[~2005-04-05 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 8:54 Problem with linux porting Atit_Shah
2005-04-05 10:01 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 13:48 Atit_Shah
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=20050405100126.GB29168@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=Atit_Shah@Satyam.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).