All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: Gilad Rom <gilad@romat.com>
Cc: "'Maciej W. Rozycki'" <macro@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: CP0 EntryLo
Date: Tue, 30 Nov 2004 10:45:23 -0800	[thread overview]
Message-ID: <41ACBFC3.1000107@embeddedalley.com> (raw)
In-Reply-To: <20041130181638.D260DEB2B8@mail.romat.com>


> Okay. I've pretty much figured out that part. What I'm puzzled
> About now is how do change the values of the CP0 EntryLo0/1
> Registers, since I've changed the DTY bits to "1" on the MEM_STCFG1
> Register (in order to set it to work in "I/O Device" mode) , 
> I need to "change bits 29:26 of CoProcessor 0 to 0xD" (Au1500 Databook
> quote)
> since the Databook doesn't specify an offset
> To these registers, I assume they're not like the other
> Registers I've been dealing with (Chip Select and GPIO).

The reason for the 0XD is because the CS is on a 36 bit physical 
address. You're in luck because the 36 bit address support went in 
the 2.6 tree a couple of days ago (I don't remember if you're using 
2.4 or 2.6, but 2.4 has the 36 bit support as well). You don't mess 
with the tlb registers yourself -- you let ioremap do its work. Take 
a look at drivers/pcmcia/au1000_generic.c and you'll see how the 
pcmcia CS is remapped. You simply pass the 36 bit phys address and 
ioremap will do its job.

If there was no 36 bit address support in the kernel, your only 
option would have been to use a wired tlb, and then you would end up 
programming the tlb registers directly. In this case there is no 
reason to do that because ioremap will handle the 36 bit phys address.

Pete

      reply	other threads:[~2004-11-30 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30  9:56 CP0 EntryLo Gilad Rom
2004-11-30  9:56 ` Gilad Rom
2004-11-30 10:24 ` Dominic Sweetman
2004-11-30 10:24   ` Dominic Sweetman
2004-11-30 16:26   ` Gilad Rom
2004-11-30 16:26     ` Gilad Rom
2004-11-30 16:37     ` Maciej W. Rozycki
2004-11-30 18:01       ` Pete Popov
2004-11-30 18:16         ` Gilad Rom
2004-11-30 18:16           ` Gilad Rom
2004-11-30 18:45           ` Pete Popov [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=41ACBFC3.1000107@embeddedalley.com \
    --to=ppopov@embeddedalley.com \
    --cc=gilad@romat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.