linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Nguyen Xuan Hoang" <jerry.nguyen@serialsystem.com.sg>
To: "Matthew Locke" <mlocke@mvista.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PCMCIA Card Service
Date: Wed, 29 Nov 2000 15:03:54 -0800	[thread overview]
Message-ID: <004f01c05a58$a60a7920$ef0fa8c0@hoangmobile> (raw)
In-Reply-To: 3A23F07A.FF2F643@mvista.com


Hi Matthew,

Thank very much for your info. I have look at your patch but it seems not
solving our problem. I would like explain more:

-  From my investigation is: there's one confliction of the interrupt:

1. The PCMCIA card service (m8xx_pcmcia) register it's interrupt handler by
calling:
    request_8xxirq(pcmcia_schlvl, m8xx_interrupt, 0, "m8xx_pcmcia", NULL);
   well, that seems logical.

2. But when an PCMCIA card plug in, it remap the memory and route it's
interrupt to the system interrupt (of course only one PCMCIA interrupt). The
problem is most of  driver using REQUEST_8XXIRQ to register the handler. For
Example the FLASH card will call IDE driver, IDE driver will call
IDE_REQUEST_IRQ to register ide_intr.
As I saw the IDE_REQUEST_IRQ call REQUEST_8XXIRQ with PCMCIA interrupt. It
fails because the interrupt already occupy by PCMCIA (see step 1).

I may be wrong...please give me some advices

Thank in advances.
Hoang

>
> yeah, I have done it.  use my patches on
> ftp://ftp.mvista.com/pub/Area51/ppc_8xx.  I still have not done a
> README, but if you have a MV support contract just contact support and
> they will help you out.


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

  reply	other threads:[~2000-11-29 23:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DKEFKEENEHPHKNLLKHCGGEEICDAA.support@mvista.com>
2000-11-29  2:57 ` PCMCIA Card Service Nguyen Xuan Hoang
2000-11-28 17:50   ` Matthew Locke
2000-11-29 23:03     ` Nguyen Xuan Hoang [this message]
2000-11-29 18:53       ` Matthew Locke

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='004f01c05a58$a60a7920$ef0fa8c0@hoangmobile' \
    --to=jerry.nguyen@serialsystem.com.sg \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mlocke@mvista.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;
as well as URLs for NNTP newsgroup(s).