From: "Mark Chambers" <markc@mail.com>
To: "Pantelis Antoniou" <panto@intracom.gr>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: m8xx_pcmcia driver ported to v2.6
Date: Thu, 12 May 2005 07:29:48 -0400 [thread overview]
Message-ID: <006101c556e5$ebbfeb10$0301a8c0@chuck2> (raw)
In-Reply-To: 4282F263.8080501@intracom.gr
> >>There is one pending problem: the M8xx does not accept
> >>access to non present ioports (an exception is triggered),
> >>which is quite common while inserting/removing cards.
> >>
> > Ah yes, I remember this problem from the 68360 days.
> >
> > This is a matter of how you set up the option register ORx
> > <snip>
> > for instance, you could turn external ack on once a card
> > was inserted.
> >
> > As I recall, some PCMCIA cards can have VERY long
> > cycles in the configuration space, so even the maximum
> > number of wait states in ORx may not be sufficient.
> >
> Unfortunately this does not work on 8xx since the PCMCIA
> port is not on a chip select. It's a different peripheral
> and always expectes a DTACK to terminate the cycle.
>
> To get over this problem we need to do something more drastic.
>
> Take a look at the __do_in_asm macro in include/asm-ppc/io.h.
>
> Regards
>
> Pantelis
>
You are right, I had forgotten that. I'd also forgotten that PCMCIA
uses negative WAIT, which should have a pull-up on it, so there
should be no problem with non-existent cards.
Another potential problem could be the Bus Monitor Timeout
being set too short and generating a TEA before a valid WAIT is
released.
Mark Chambers
prev parent reply other threads:[~2005-05-12 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 15:41 m8xx_pcmcia driver ported to v2.6 Marcelo Tosatti
2005-05-10 22:29 ` Mark Chambers
2005-05-12 6:06 ` Pantelis Antoniou
2005-05-12 11:29 ` Mark Chambers [this message]
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='006101c556e5$ebbfeb10$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=panto@intracom.gr \
/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).