U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yuli Barcohen <yuli@arabellasw.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Motorola PPC827x
Date: Fri, 31 Oct 2003 17:33:29 +0200	[thread overview]
Message-ID: <001501c39fc4$5d6ae9c0$bbf175c0@privatesystem> (raw)
In-Reply-To: 37FB7AA6F5F9814FB634A7BF4C35A6F501213C14@ESEALNT442.al.sw.ericsson.se

>>>>> Matias Sundman writes:

Matias> I have a PQ2FADS_VR ( ppc8275 ) board from motorola which
has a 66000000 Hz clock.
Matias> Is it worthwhile to insert this anomaly to the u-boot
code? I have done changes
Matias> in MPC8260ADS.h file in order to make it run for me.

What do you mean by "anomaly"? If the only thing you had to change
is clock frequency, I'd say it's OK.
My MPC8260ADS board, for example, uses 40MHz clock so I too have
to change the default value.
I tried to set default values to the frequencies of the
oscillators the boards are shipped with. MPC826xADS
are shipped with 66MHz clock while PQ2FADS-ZU is shipped with
100MHz. PQ2FADS-VR is shipped
with 66MHz clock because VR chips are limited to 66MHz frequency.
It's the only difference between ZU
and VR boards. Do you think we have to create additional
CFG_ADSTYPE for VR boards to handle this
difference? Changing clock in MPC8260ADS.h looks simpler.
--
==================================================================
======
      Yuli Barcohen       | Phone +972-9-765-1788 |  Software
Project Leader
 yuli at arabellasw.com | Fax     +972-9-765-7494 | Arabella
Software, Israel
==================================================================
======

      reply	other threads:[~2003-10-31 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 18:22 [U-Boot-Users] Motorola PPC827x Matias Sundman
2003-10-31 15:33 ` Yuli Barcohen [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='001501c39fc4$5d6ae9c0$bbf175c0@privatesystem' \
    --to=yuli@arabellasw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox