From: David Hawkins <dwh@ovro.caltech.edu>
To: stonepine <stonepine@126.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 11-16-05 2.6.14 on AMCC Yosemite boar d(PCI-IDE card boot error)
Date: Thu, 14 Sep 2006 11:01:00 -0700 [thread overview]
Message-ID: <450998DC.1010604@ovro.caltech.edu> (raw)
In-Reply-To: <450996FB.5050408@126.com>
> The problem was addressed with your help, and I do really appreciate your help.
Great!
I hope you learned your lesson though: when something breaks, make
sure to re-test using the head of the git repo. Of course that may
break something too, but most other developers will also be working
from the head, so can probably reproduce your problem.
(Or will be more likely to listen to any complaints).
Also its worth writing a couple of simple drivers; one that
maps a PCI IO memory space and another that maps PCI memory
space. That way you can cause the machine check in a very
basic driver, i.e., your problem had nothing to do with
your specific card.
Take a look at the LNX-723 document and code, I wrote
it while using a Yosemite board, but have moved on
to a Freescale MPC8349E device, since the 440EP wasn't
going to work for my application:
http://www.ovro.caltech.edu/~dwh/correlator/cobra_docs.html
Here's a copy of my test notes:
http://www.ovro.caltech.edu/~dwh/powerpc_440ep.pdf
Cheers
Dave
next prev parent reply other threads:[~2006-09-14 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 3:44 11-16-05 2.6.14 on AMCC Yosemite boar d(PCI-IDE card boot error) Stephen Yee
2006-09-13 20:11 ` Stephen Yee
2006-09-14 0:44 ` David Hawkins
2006-09-14 17:52 ` stonepine
2006-09-14 18:01 ` David Hawkins [this message]
2006-09-14 0:52 ` Wolfgang Denk
2006-09-20 15:55 ` Unable to mount jffs2 Mathews, Phil
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=450998DC.1010604@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=linuxppc-embedded@ozlabs.org \
--cc=stonepine@126.com \
/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;
as well as URLs for NNTP newsgroup(s).