Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Ladislav Michl <ladislav.michl@hlubocky.del.cz>
Cc: Ian Chilton <ian@ichilton.co.uk>, linux-mips@oss.sgi.com
Subject: Re: 2.4.16 success on Indy (was Re: 2.4.16 success on Decstation 5000/150)
Date: Mon, 3 Dec 2001 19:25:43 +0100	[thread overview]
Message-ID: <20011203192543.A10394@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0112031726021.2278-100000@hlubocky.del.cz>

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

On Mon, Dec 03, 2001 at 05:34:40PM +0100, Ladislav Michl wrote:
> sure :-) IRQ 8 is FIFO full and was never used (and to be honest, i don't
> know what that irq is used for). before Wed, 21 Nov 2001 17:49:32 +0100
> it was General purpose local interrupt - this one was also never
> used. see include/asm-mips/sgi/sgint23.h for more info.
> 
> i have no clue, why you're getting this interrupt. it works pretty well
> for me...

Ok - the IRQ8 get enabled because i have CONFIG_RTC set and in
drivers/char/rtc.c around line 730 it requests:

if(request_irq(RTC_IRQ, rtc_interrupt, SA_INTERRUPT, "rtc", NULL))

Immediatly afterwards the massive ammount of IRQs. With 100Hz and 160
Chars across the screen - I would expect 1-2 lines/s on the screen.
Instead the screen fills up within tens of seconds which seems to me
like non acked IRQ.

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
Nine nineth on september the 9th              Welcome to the new billenium

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-12-03 19:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02 23:03 2.4.16 success on Decstation 5000/150 Florian Lohoff
2001-12-03  0:00 ` 2.4.16 success on Indy (was Re: 2.4.16 success on Decstation 5000/150) Ian Chilton
2001-12-03 13:37   ` Florian Lohoff
2001-12-03 16:19     ` Ian Chilton
2001-12-03 16:34       ` Ladislav Michl
2001-12-03 18:25         ` Florian Lohoff [this message]
2001-12-03 22:44           ` Ian Chilton
2001-12-07  2:31             ` Ralf Baechle
2001-12-08 16:35               ` Ladislav Michl
2001-12-10 17:17                 ` [PATCH] timer fix (was: Re: 2.4.16 success on Indy...) Ladislav Michl
2001-12-04  7:41           ` 2.4.16 success on Indy (was Re: 2.4.16 success on Decstation 5000/150) Ladislav Michl
2001-12-04  8:59             ` Florian Lohoff
2001-12-04  9:11               ` Geert Uytterhoeven
2001-12-04  9:18               ` Ladislav Michl
2001-12-05  1:10                 ` Florian Lohoff
2001-12-04  9:26 ` 2.4.16 success on Decstation 5000/150 Houten K.H.C. van (Karel)
2001-12-04 11:44   ` Maciej W. Rozycki
2001-12-04 12:04     ` Martin Schulze
2001-12-04 12:20       ` Maciej W. Rozycki
2001-12-04 23:31         ` Klaus Naumann

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=20011203192543.A10394@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=ian@ichilton.co.uk \
    --cc=ladislav.michl@hlubocky.del.cz \
    --cc=linux-mips@oss.sgi.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