From: Dan Brown <dan.brown@nrl.navy.mil>
To: Brian O'Dell <brian@clarionsensing.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DOCBoot doesn't compile
Date: Wed, 29 Jun 2005 14:47:32 -0400 [thread overview]
Message-ID: <42C2ECC4.1000705@nrl.navy.mil> (raw)
In-Reply-To: <42C2EAEE.8040204@clarionsensing.com>
Brian O'Dell wrote:
> After reading through the doc_bootstub.S a bit, it looks like my system
> isn't even getting to the interrupt handler. I've installed to 18h and
> 19h. Both with the same result: The system locks hard right after it
> exits from the SPL. Could docboot be clobbering something important
> when it loads the interrupt handler? I'm assuming that it isn't getting
> to the interrupt handler because I don't get the "Kernel Loading..."
> message. Is my theory plausible or likely?
It's been a while since I've actually run DOCBoot (I've been working on
other stuff), so I just built and installed it on my device from the
latest CVS as a sanity check. I get the same hard lockup as you do.
I'll let you know when I've found the problem. Needless to say, I'm a
bit embarassed to have checked in code this broken and let it sit that
way in the repository for several months :(
-Dan
next prev parent reply other threads:[~2005-06-29 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 18:05 DOCBoot doesn't compile Brian O'Dell
2005-06-27 18:50 ` Dan Brown
2005-06-28 16:54 ` Brian O'Dell
2005-06-28 19:12 ` Dan Brown
2005-06-28 21:39 ` Brian O'Dell
2005-06-29 18:39 ` Brian O'Dell
2005-06-29 18:47 ` Dan Brown [this message]
2005-06-29 20:12 ` Dan Brown
2005-06-29 21:50 ` Brian O'Dell
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=42C2ECC4.1000705@nrl.navy.mil \
--to=dan.brown@nrl.navy.mil \
--cc=brian@clarionsensing.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox