All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patches for 85xx question
Date: Wed, 12 Dec 2007 13:45:55 -0800	[thread overview]
Message-ID: <47605693.7020202@ovro.caltech.edu> (raw)
In-Reply-To: <f87675ee0712121337j2b87be4fgbea78b42b3f37301@mail.gmail.com>

Hi Robert,

> Hey thanks, what a long strange trip its been ;-) .

Sounds more like the trip you should have expected.
That'll teach you for being optimistic, eh
I get burned for being that way too - an engineering
trait I guess.

> For the memory issues, we found a memory chip (Micro 533MHZ) that
> works 95% of the time, and the hardware guys are working with
> Freescale support for our second revision, and in fact have already
> improved things considerably on other chips. That's good enough to
> continue the project ;-) .

Feel free to provide details on your solutions.

The Freescale design documents are sparce in some places,
incorrect in others. AN2931 which contains the design
recommendations for boards based on the 83xx series processor
has been revised multiple times since I started work on my board.
And even now, there are other valid ways to implement parts
of the design.

> The PCI issues were resolved also by hardware, via using "Asynchronous
> mode" instead of "Synchronous mode", thereby routing CLKOUT to
> PCI1_CLK. See the "4.4.3.17 PCI Clock Selection" section if
> interested.

So you have clocking issues?

> So the latest 2.6.24RCx kernel's now booting, and all that's left is a
> few driver issues. That and submitting patches ;-) .

Glad to hear your 'Tuna' can swim.
Sure beats being stuffed into a tin can :)

Cheers,
Dave

  reply	other threads:[~2007-12-12 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 18:31 [U-Boot-Users] Patches for 85xx question robert lazarski
2007-12-12 21:15 ` David Hawkins
2007-12-12 21:37   ` robert lazarski
2007-12-12 21:45     ` David Hawkins [this message]
2007-12-12 22:17 ` Kumar Gala

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=47605693.7020202@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --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.