From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: timebase_interrupts on MPC8xx ???
Date: Thu, 11 Oct 2001 10:24:06 +0200 [thread overview]
Message-ID: <3BC55726.AAC2D093@imc-berlin.de> (raw)
Hi there,
I pulled linuxppc_2_4_devel yesterday, built and ran it on my MPC8xx
board.
Now I get load of
timebase_interrupt()
timebase_interrupt()
timebase_interrupt()
messages, which come from
/* A place holder for time base interrupts, if they are ever enabled. */
void timebase_interrupt(int irq, void * dev, struct pt_regs * regs)
{
printk ("timebase_interrupt()\n");
}
in arch/ppc/kernel/m8xx_setup.c.
I've never seen them before, so I guess they were never enabled.
Are they enabled now? Why? Hardly just for making noise! ;-)
Cheers,
Steven Scholz
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-11 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 8:24 Steven Scholz [this message]
2001-10-11 17:53 ` timebase_interrupts on MPC8xx ??? Dan Malek
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=3BC55726.AAC2D093@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).