From: Dan Malek <dan@netx4.com>
To: "Mark S. Mathews" <mark@absoval.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RPXLite 823 PCMCIA troubles
Date: Tue, 30 Nov 1999 21:51:22 -0500 [thread overview]
Message-ID: <38448D2A.E11E4ADF@netx4.com> (raw)
In-Reply-To: Pine.LNX.3.96.991130133128.22618B-100000@tristar.cc.absoval.com
Mark S. Mathews wrote:
>
> Howdy Folks,
>
> We've been working with the embedded 2.2.13 kernel on an RPX-Lite CW with
> a XPC823ZT66A processor running at the 50MHz/8MHz setting.
It's not only the RPX Lite.....I have a variety of 8xx boards
and when I have trouble like this with a particular card, it
occurs in all of the boards.
> ............ but our
> accesses to the common memory regions of the card are twitchy.
Same thing I have seen. The I/O and attribute regions seem
to work OK, but memory regions don't.....on more than one
type of card.
> .....but eventually we wind up with a machine-check.
Which points to some kind of bus timing or protocol problem.
> runs well on the x86, our PowerBook, and on a different 860 based platform
> (non-Linux, no MMU) so we're fairly confident it isn't the code.
Well now, that's interesting (the no MMU, not the non-Linux
part :-). With the MMU disabled, the accesses behave as guarded.
This is something I have not properly implemented on the 8xx,
and with my somewhat sloppy use of eieio() and synchronization,
I am always waiting for this to come back and haunt me. Notice
how I buried this important fact in this paragraph. I will now
properly implement this (yet tonight). Tell me the kernel version
you are using and I will send some updates for your testing.
How does someone (like me :-) determine what a PCMCIA interface
in something like a PowerBook uses for bus timing?
> One specific question...when setting up the PCMCIA bus timings, the 823
> book lists the settings in units of "clock cycles". Which clock?
It is the CLKOUT (system/bus) clock. On the 66MHz processor,
this better be 33 MHz (processor clock / 2). For 50 MHz or
less, the CLKOUT is the processor clock.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-01 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-30 19:43 RPXLite 823 PCMCIA troubles Mark S. Mathews
1999-12-01 2:51 ` Dan Malek [this message]
1999-12-01 3:41 ` Mark S. Mathews
1999-12-01 4:08 ` Dan Malek
1999-12-02 20:49 ` Mark S. Mathews
1999-12-02 21:10 ` Dan Malek
1999-12-01 4:24 ` Alan Mimms
1999-12-01 17:21 ` Dan Malek
1999-12-01 17:46 ` Alan Mimms
-- strict thread matches above, loose matches on Subject: below --
1999-12-03 4:31 Brian Kuschak
1999-12-03 6:32 ` Mark S. Mathews
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=38448D2A.E11E4ADF@netx4.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mark@absoval.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).