linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: timebase_interrupts on MPC8xx ???
Date: Thu, 11 Oct 2001 13:53:10 -0400	[thread overview]
Message-ID: <3BC5DC86.551DAF48@mvista.com> (raw)
In-Reply-To: 3BC55726.AAC2D093@imc-berlin.de


Steven Scholz wrote:

> I pulled linuxppc_2_4_devel yesterday, built and ran it on my MPC8xx
> board.

I pulled it today and it won't boot on my 860....I've been trying
to fix it.  There is no reason for the timebase interrupts unless
somehow an external interrupt was routed there.  All of the interrupts
are disabled in the clock control registers.....have been forever :-).

I will post another message when I get it booting again.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-10-11 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  8:24 timebase_interrupts on MPC8xx ??? Steven Scholz
2001-10-11 17:53 ` Dan Malek [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=3BC5DC86.551DAF48@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.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;
as well as URLs for NNTP newsgroup(s).