From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Shinkyu Kang <ksk4097@gmail.com>
Cc: meta-freescale <meta-freescale@yoctoproject.org>
Subject: Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().
Date: Fri, 03 May 2013 12:53:16 -0700 [thread overview]
Message-ID: <518415AC.2010303@boundarydevices.com> (raw)
In-Reply-To: <CAPqpt39vUSFQXsUJTg=pMuh8ot77BcWjydLk0w6wfhFL89BH4A@mail.gmail.com>
Hi Shinkyu,
On 05/03/2013 12:46 PM, Shinkyu Kang wrote:
> Hi, Eric,
> Thank you for the hint.
> >> Does your Rev D board have 1.2 silicon?
> >> You can see this during U-Boot startup:
> >> CPU: Freescale i.MX6Q rev1.2 at 792 MHz
>
> Yes. I can see the message.
> Also, when I using the kernel 3.0.35-gb0b02db-dirty,
> the debug message shows "CPU identified as i.MX6Q, silicon rev 1.2".
That's what I thought.
> But, in 3.4.34 kernel, I couldn't find the mesage.
> Is there any initalization code for "i.MX6Q, silicon rev 1.2".
These are off-topic for the meta-freescale list.
Please contact me privately, and bring in the WRS support
team.
There are a variety of conditionals for CPU revisions
in the kernel startup, and either Freescale's git
repository or ours are the places to start reviewing
them vs. the Wind River kernel.
Regards,
Eric
next prev parent reply other threads:[~2013-05-03 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 5:32 [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge() Shinkyu Kang
2013-05-03 15:47 ` Eric Nelson
2013-05-03 15:50 ` Eric Nelson
2013-05-03 19:46 ` Shinkyu Kang
2013-05-03 19:53 ` Eric Nelson [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-30 23:02 Shinkyu Kang
2013-05-01 1:24 ` Eric Nelson
2013-05-01 2:35 ` Shinkyu Kang
2013-05-01 23:23 ` Otavio Salvador
2013-05-02 0:05 ` Fabio Estevam
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=518415AC.2010303@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=ksk4097@gmail.com \
--cc=meta-freescale@yoctoproject.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.