linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: gopi krishna <mgopik@yahoo.com>
To: linuxppc-dev@lists.linuxppc.org
Cc: govindan@tejasnetworks.com, dhanush@tejasnetworks.com
Subject: Re: Problem with PCMCIA and RPXCLASSIC
Date: Wed, 27 Dec 2000 22:15:58 -0800 (PST)	[thread overview]
Message-ID: <20001228061558.39005.qmail@web11107.mail.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]

Hi..

  We got the IBM microdrive on pcmcia up on RPXclassic
with the changes(given in patch file as attatchment).

Kernel: 2.2.14
pcmcia-cs:3.1.22

This, unlike dan's implementation, uses the card
services also.  There are mainly 3 changes:
1. _IO_BASE
2. Hooking the IRQLVL of PCMCIA PGCR to 9(9 is used by
ide.. else we get a lost interrupt error).
3. ide_ack_intr to clear PCSR.

M. Gopi Krishna
Tejas Networks India Ltd
www.tejasnetworks.com
Email:gopi@tejasnetworks.com
-----------------------------------

Matthew Locke wrote:

> >Then we gave _IO_BASE = 0x80000000
> >This still did not work and the kernel panics.  We
had to >comment out
> >a line in ll_rw_blk.c( where and outb_p is
called)..
> >After this the kernel comes up.
>
> So, IO_BASE = 0x80000000 does work, ll_rw_blk.c is
an unrelated bug.

What are you guys using for a kernel?  This outb_p
"bug" was fixed
in ancient times (or you didn't properly configure the
kernel).


> It may be a little confusing, but since it works for
me I doubt there is a
> goof up. The confusing part is that there is code in
there to bypass card
> services for ATA cards.

Yes, this works.  It sounds like you are mixing the
internal ATA hack
with card services.  You can't use both........

> >I HAVE READ IN THE MAILING LIST from Dan dated TUE
02, may 2000
> >that he has successfully used IBM Micro drive with
MPC860 PCMCIA.
> >has anybody got the detail information ?
>
> I don't think Dan uses card services.  He has code
in the kernel that
> connects the ide driver directly to the 8xx pcmcia
controller.

That's right, no card services when I wrote that
message.  I just
used the PCMCIA interface as a dedicated ATA
interface.  The purpose
was simply to verify the hardware would work
correctly, and to provide
a method for embedded systems to use this interface
directly without
card services.


        -- Dan



Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/

[-- Attachment #2: kernel-disc.patch --]
[-- Type: application/x-unknown, Size: 8254 bytes --]

[-- Attachment #3: pcmcia-disc.patch --]
[-- Type: application/x-unknown, Size: 2446 bytes --]

             reply	other threads:[~2000-12-28  6:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28  6:15 gopi krishna [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-21 18:38 Problem with PCMCIA and RPXCLASSIC Matthew Locke
2000-12-21 19:15 ` Dan Malek
2000-12-19 19:06 Matthew Locke
2000-12-20 17:38 ` Govindan
2000-12-19 13:22 Govindan

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=20001228061558.39005.qmail@web11107.mail.yahoo.com \
    --to=mgopik@yahoo.com \
    --cc=dhanush@tejasnetworks.com \
    --cc=govindan@tejasnetworks.com \
    --cc=linuxppc-dev@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).