linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
Cc: Ruedi Hofer <ruedi.hofer@ascom.ch>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCMCIA support for 860
Date: Tue, 04 Apr 2000 19:33:45 -0400	[thread overview]
Message-ID: <38EA7BD9.C24774EB@embeddededge.com> (raw)
In-Reply-To: kfyhfdiw06w.fsf@kieraypc01.p.y.ki.era.ericsson.se


Marcus Sundberg wrote:
>
> Ruedi Hofer <ruedi.hofer@ascom.ch> writes:

> > Does someone have a clue on that? Is request_irq and request_8xxirq related??

Sort of.  The MPC8xx has an internal interrupt controller.  The
Linux community seems to think the world is 8259s and PCI/ISA bus.
Mapping request_irq into the 8xx interrupt controller was attempted,
but didn't provide the proper results.  The request_8xxirq function
is used by all integrated device drivers (serial, Ethernet, TDM/audio,
USB, SPI, I2C, PCMCIA, general purpose I/O pins, etc.), as they know
they are using the internal interrupt controller.

In the case of boards with PCI/ISA bridges, the request_irq is also
enabled because there is a downstream 8259 controller.  Not defining
this when there is no 8259 causes drivers that would attempt to use
this to fail.  It is nice to know this at build time, rather than
wondering why things are crashing or not working once the system is
booted.

This also presents a challenge for PCMCIA devices.  All of these drivers
(or supporting functions) want to install interrupt handlers using
request_irq, which doesn't make sense on the 8xx.  I have the ATA/IDE
patch to install the interrupt handler, but other devices may also need
interrupt handler patches.


	-- Dan

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

  reply	other threads:[~2000-04-04 23:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-04  9:49 Re: PCMCIA support for 860 Ruedi Hofer
2000-04-04 11:54 ` Marcus Sundberg
2000-04-04 23:33   ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-23  9:58 Shuangjun Zhu
2000-05-22  9:24 Shuangjun Zhu
2000-05-19  8:35 Shuangjun Zhu
2000-04-06 10:39 Ruedi.Hofer
2000-04-06 12:23 ` Marcus Sundberg
2000-04-05 16:21 Ruedi.Hofer
2000-04-06  9:07 ` Marcus Sundberg
2000-04-04 11:52 Ruedi Hofer
2000-04-04 13:23 ` Marcus Sundberg
2000-04-03  7:55 Ruedi.Hofer
2000-04-03 17:01 ` Marcus Sundberg
2000-04-03 19:55   ` 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=38EA7BD9.C24774EB@embeddededge.com \
    --to=dan@netx4.com \
    --cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ruedi.hofer@ascom.ch \
    /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).