Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@pacbell.net>
To: jim@jtan.com
Cc: linux-mips@oss.sgi.com
Subject: Re: pcmcia (again)
Date: Tue, 18 Sep 2001 00:06:44 -0700	[thread overview]
Message-ID: <3BA6F284.50506@pacbell.net> (raw)
In-Reply-To: 20010918024814.A6517@neurosis.mit.edu

Jim Paris wrote:
>>>Am I misunderstanding something here?  Is there some simple way to get
>>>the PCMCIA driver to use isa_slot_offset when checking and
>>>requesting memory regions?  I tried adding that offset to the
>>>check_mem_resource, request_mem_region, and release_mem_region calls,
>>>and changing all of the readx/writex() calls to isa_readx/isa_writex(),
>>>but things still don't work right.
>>>
> 
> .. 
> 
> Success!!
> 
> The main problem was that I had subtly broken the ioremap function
> while trying to update the linux-vr tree to 2.4.5ish.  Doh!
> 
> A second problem is that the pcmcia drivers needed to add
> isa_slot_offset when calling {check,request,release}_mem_region
> -- but the readx/writex calls do _not_ need this offset added.
> (So this must be handled by the ioremap.  I still don't fully
> understand when or where this remapping is done, but I know it's
> happening.)
> 
> And it works!
> 
> This means that I now have a working 2.4.5 kernel on my Mobilon Tripad
> (aka Vadem Clio) with a functional compact flash and wireless ethernet
> card.  I'm quite happy.  Now I just need to build some binaries.
> 
> Pete, thanks for your help; it pointed me in the right direction.
> 
Good to hear that you found the problems.  If your patch to use isa_slot_offset 
doesn't get accepted, you might want to try to figure out if there's any way to 
limit your changes to your board's specific files. That way you won't have to 
carry patches around from one kernel version to another. I think this is now the 
second mips board with pcmcia support.

BTW, I have a LE ramdisk which runs linuxrc, loads pcmcia drivers, starts 
cardmgr, and exits. The kernel then mounts the real root fs which is /dev/hda1 
in my case (pcmcia ata card).  Let me know if you need it.

Pete

  reply	other threads:[~2001-09-18  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17  4:19 pcmcia (again) Jim Paris
2001-09-17  5:22 ` Pete Popov
2001-09-17 16:31   ` Jim Paris
2001-09-18  4:00     ` Pete Popov
2001-09-18  6:48       ` Jim Paris
2001-09-18  7:06         ` Pete Popov [this message]
2001-09-18  7:45           ` Jim Paris

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=3BA6F284.50506@pacbell.net \
    --to=ppopov@pacbell.net \
    --cc=jim@jtan.com \
    --cc=linux-mips@oss.sgi.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