linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: jmouro@iol.pt
To: linuxppc-embedded@lists.linuxppc.org
Subject: PCMCIA polling!?!
Date: Wed, 11 Jun 2003 15:51:55 +0100	[thread overview]
Message-ID: <5bf7b05c1bab.5c1bab5bf7b0@iol.pt> (raw)


Hello,
I'm working on a embedded system with a  TQM860L, and a I have a doubt that perhaps you might answer.
I've 2 signals related with system defects (power supply defects) connected to PCMCIA channel II (IPBx). Is there a way to check if those signals where triggered without polling them? Like in interrupt lines? In that way I could
Thanks for your attention.
jmouro


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

             reply	other threads:[~2003-06-11 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 14:51 jmouro [this message]
2003-06-11 20:31 ` PCMCIA polling!?! Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-06-12  9:15 jmouro
2003-06-12 10:09 ` Wolfgang Denk

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=5bf7b05c1bab.5c1bab5bf7b0@iol.pt \
    --to=jmouro@iol.pt \
    --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).