From: rusko.peter@prolan•hu (Peter Rusko)
To: linux-arm-kernel@lists•infradead.org
Subject: MX28 fec clock frequency
Date: Tue, 10 Jan 2012 16:39:37 +0100 [thread overview]
Message-ID: <4F0C5BB9.3070203@prolan.hu> (raw)
In-Reply-To: <20120110140043.GC26599@S2101-09.ap.freescale.net>
On 2012-01-10 15:00, Shawn Guo wrote:
> Another point worth checking is bit field ATIME_INC of register
> HW_ENET_MAC_ATIME_INC. It should be 25 if your CLK_ENET_TIME runs
> at 40 MHz.
>
No, that was set correctly. Finally, I've found my mistake. I've
overwritten the other bits when writing the divider so xtal clock was
selected automatically.
Silly little mistake, isn't it? :) Anyway, thank you for your help.
--
Rusk? P?ter
Fejleszt?m?rn?k
Prolan Zrt. / Prolan Co.
Hungary 2011 Budakal?sz, Szentendrei ?t 1-3.
Tel./Phone: +36 20 954 3118
Fax: +36 26 540 420
E-mail: rusko.peter at prolan.hu
Web: www.prolan.hu
Timezone:CET
prev parent reply other threads:[~2012-01-10 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 11:08 MX28 fec clock frequency Peter Rusko
2012-01-08 3:32 ` Shawn Guo
2012-01-09 14:07 ` Peter Rusko
2012-01-10 8:21 ` Shawn Guo
2012-01-10 13:08 ` Peter Rusko
2012-01-10 14:00 ` Shawn Guo
2012-01-10 15:39 ` Peter Rusko [this message]
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=4F0C5BB9.3070203@prolan.hu \
--to=rusko.peter@prolan$(echo .)hu \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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