All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Scott A McConnell <samcconn@cotw.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: IRQ questions
Date: Fri, 20 Apr 2001 19:00:17 -0300	[thread overview]
Message-ID: <20010420190017.B7282@bacchus.dhis.org> (raw)
In-Reply-To: <3AE081E3.434E9126@cotw.com>; from samcconn@cotw.com on Fri, Apr 20, 2001 at 11:37:24AM -0700

On Fri, Apr 20, 2001 at 11:37:24AM -0700, Scott A McConnell wrote:

> In 2.4.0-test 5 the file arch/mips/kernel/irq.c used to be built. Under
> 2.4.3 it no longer is. However, it appears it was renamed to old_irg.c
> and a new irq.c was created. I also noticed that an i8259.c files was
> added at some point. However, it does not seem to match the code that
> was in irq.c.

Not entirely, yet.  The idea is that a board can register a structure
containing information on how to handle an interrupt with the new irq.c
So a board which has PC-style i8259 PICs could call init_i8259_irqs
which in turn would register handlers for the interrupts 0 - 15 which
would be handle in i8259; handler for other interrupts controllers could
be registered also.

> Are there any notes available that explain how to convert from old style
> IRQ's to new?
> What are we suppose to do with the new irq.c which is not being used?

The IRQ changes should be considered work in progress; until the new
interrupt code you should just follow the example given by the many
existing implementations.

> I have a 2.4.3 kernel booting. I copied the old  arch/mips/kernel/irq.c
> to my target directory and changed

One valid solution ...  Still.  We want to eleminate all this code
duplication for no good reason.

> a few other things to get everything to compile. As long as I do not try
> to use a serial port everything seems to be working.  I booted with a
> frame buffer and started X.  The mouse and keyboard worked so some of my
> IRQ's appear to be working.
> 
> When I start the serial port things seem to go fine untile it trys to
> write the port at which point it starts running very slowly. Which is
> what make me think the kernel is being overcome with interrupts.

Or you don't receive interrupts at all.

  Ralf

  reply	other threads:[~2001-04-20 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 18:37 IRQ questions Scott A McConnell
2001-04-20 22:00 ` Ralf Baechle [this message]
2001-04-23 23:21   ` Scott A McConnell
2001-04-23 21:48     ` Ralf Baechle
     [not found]     ` <3AE49FD1.2BEAFA53@mvista.com>
2001-04-24 14:38       ` Scott A McConnell

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=20010420190017.B7282@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=samcconn@cotw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.