linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <damm@opensource.se>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCMCIA on an MPC860
Date: Fri, 23 Aug 2002 11:32:20 +0200	[thread overview]
Message-ID: <3D660124.9FB4BD2E@opensource.se> (raw)
In-Reply-To: 3D64DA41.3000104@cambridgebroadband.com


I've not used the driver together with a 2.4 kernel,
so I'm not sure how well modules from pcmcia-cs plays
with pcmcia stuff in the kernel.

Linux-2.4.19 has a version of the driver that
Matthew Locke modified and bugfixed. Maybe that one
works better with 2.4 kernels.

What happens if you decode the OOPS?

To get symbols, use the file System.map from
the kernel together with the map generated by
"insmod -m".
Or use /proc/ksysms from the running system.

"cardctl ident" and "cardctl status" only reads
the CIS and checks the pin status. (Correct me
if I remember wrong).

I think it will be the ide-driver that starts
accessing the IO-space. Maybe that doesn't work.

/ Magnus

Alex Zeffertt wrote:
>
> All,
>
> Has anybody had any luck getting PCMCIA to work on an MPC860?
>
> I have a custom MPC860 board, with a single PCMCIA socket connected to Slot B.  This is what I have
> so far done:
>
> 1.
> Downloaded pcmcia-cs-3.2.0.tar.gz
> 2.
> Added board specific definitions in modules/m8xx_pcmcia.c for
>                 hardware_enable()
>                 hardware_disable()
>                 voltage_set()
>                 socket_get()
> 3.
> Cross compiled for the 8xx.
> 4.
> In my kernel (linux-2.4.4-2001-11-24 from Denx) I added the following lines
>                 include/asm-ppc/<board>.h:
>                         /* define IO_BASE for pcmcia */
>                         #define _IO_BASE 0x80000000
>                         #define _IO_BASE_SIZE (1024*64)
>                 arch/ppc/mm/init.c:
>                         void __init MMU_init(void) {
>                         ...
>                         ioremap(_IO_BASE,_IO_BASE_SIZE);
>
>         ...as suggested by Magnus Damm in
>         http://lists.linuxppc.org/linuxppc-embedded/200005/msg00227.html
>
> HOWEVER,
>
> 5.      When I boot my board with a Flash card in the PCMCIA slot, and I run:
>         /etc/rc.d/rc.pcmcia start
>         I find that ide_cs.o causes an Oops when it calls ide_register().  "cardctl status"
>         and "cardctl ident" work though.
>
> Can anybody suggest what I'm doing wrong?
>
> Thanks in advance,
>
> Alex

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

      parent reply	other threads:[~2002-08-23  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22 12:34 PCMCIA on an MPC860 Alex Zeffertt
2002-08-23  8:09 ` Steven Scholz
2002-08-23  8:51   ` Alex Zeffertt
2002-08-23  9:07     ` Steven Scholz
2002-08-23  9:20     ` shaowei dai
2002-08-23  9:32       ` Alex Zeffertt
     [not found]     ` <20020823090906.3511611822@denx.denx.de>
2002-08-23  9:24       ` Alex Zeffertt
2002-08-23  9:32 ` Magnus Damm [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=3D660124.9FB4BD2E@opensource.se \
    --to=damm@opensource.se \
    --cc=ajz@cambridgebroadband.com \
    --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).