Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Matej Kupljen <matej.kupljen@ultra.si>
To: linux-mips@linux-mips.org
Subject: PCMCIA on AU1200
Date: Tue, 31 Jan 2006 11:39:13 +0100	[thread overview]
Message-ID: <1138703953.7932.36.camel@localhost.localdomain> (raw)

Hi

I am trying to use PCMCIA on a DBAU1200 with 16bit card.
>From the docs for the board, I see that the PCMCIA interface 
is on CE[3], but the value of the mem_staddr3 is
0x1000000.

Looking at the Linux source code, I see that the PCMCIA is
ioremap-ed to 0xf00000000 (36 bit). It also uses PSEUDO
addresses for the skt->phys_attr and skt->phys_mem.

At what (physical) address can I find the card's I/O space,
so I can use tools like devmem2 to see the cards CIS?
Should I configure mem_stadd3 to same other value?
To 0xf0000000?

BR,
Matej

WARNING: multiple messages have this Message-ID (diff)
From: Matej Kupljen <matej.kupljen@ultra.si>
To: linux-mips@linux-mips.org
Subject: PCMCIA on AU1200
Date: Tue, 31 Jan 2006 11:39:13 +0100	[thread overview]
Message-ID: <1138703953.7932.36.camel@localhost.localdomain> (raw)
Message-ID: <20060131103913.lf73LY3O70KAEvYTV1Sga1L613M84pEADrlyFCB4rnA@z> (raw)

Hi

I am trying to use PCMCIA on a DBAU1200 with 16bit card.
From the docs for the board, I see that the PCMCIA interface 
is on CE[3], but the value of the mem_staddr3 is
0x1000000.

Looking at the Linux source code, I see that the PCMCIA is
ioremap-ed to 0xf00000000 (36 bit). It also uses PSEUDO
addresses for the skt->phys_attr and skt->phys_mem.

At what (physical) address can I find the card's I/O space,
so I can use tools like devmem2 to see the cards CIS?
Should I configure mem_stadd3 to same other value?
To 0xf0000000?

BR,
Matej

             reply	other threads:[~2006-01-31 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 10:39 Matej Kupljen [this message]
2006-01-31 10:39 ` PCMCIA on AU1200 Matej Kupljen
2006-01-31 14:03 ` Ulrich Eckhardt
2006-01-31 19:41   ` Matej Kupljen
2006-01-31 20:49     ` Jordan Crouse

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=1138703953.7932.36.camel@localhost.localdomain \
    --to=matej.kupljen@ultra.si \
    --cc=linux-mips@linux-mips.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