From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] sypcr double written
Date: Tue, 23 May 2006 16:47:42 -0400 [thread overview]
Message-ID: <447374EE.5050301@smiths-aerospace.com> (raw)
In-Reply-To: <200605232240.05529.antonio.dibacco@aruba.it>
Antonio Di Bacco wrote:
> wdt_mpc8xx.c is in the kernel, in the drivers/char/wdt_mpc8xx.c
>
> On Tuesday 23 May 2006 22:31, Wolfgang Denk wrote:
>> In message <200605232124.05181.antonio.dibacco@aruba.it> you wrote:
>>> I saw that in cpu_init_f the sypcr is written and it is also written in
>>> the init of wdt_mpc8xx.o but this should not be possible according to the
>>> MPC885 Reference Manual.
>> It is not possible, but then: what's wdt_mpc8xx.o? This is not part
>> of U-Boot.
>>
>>> For sure there is an explanation for this, anyone knows?
>> Um... and if you're talking about any Linux kernel code - who says
>> that it's been booted by U-Boot, or that the boot loader initialized
>> the SYPCR?
>>
>> Best regards,
>>
>> Wolfgang Denk
Well, strictly speaking it _is_ possible to write the SYPCR more than
once, it just doesn't do anything because the CPU ignores all but the
first write. Whatever wdt_mpc8xx.o writes is ignored in this case.
Best regards,
gvb
P.S. Please don't top post.
next prev parent reply other threads:[~2006-05-23 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 19:24 [U-Boot-Users] sypcr double written Antonio Di Bacco
2006-05-23 20:31 ` Wolfgang Denk
2006-05-23 20:40 ` Antonio Di Bacco
2006-05-23 20:47 ` Jerry Van Baren [this message]
2006-05-23 21:10 ` Wolfgang Denk
2006-05-24 11:59 ` [U-Boot-Users] " antonio.dibacco
2006-05-24 13:00 ` Wolfgang Denk
2006-05-24 13:52 ` antonio.dibacco
2006-05-24 16:27 ` Wolfgang Denk
2006-05-25 19:39 ` Antonio Di Bacco
2006-05-28 22:20 ` Wolfgang Denk
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=447374EE.5050301@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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.