All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm@momenco.com>
To: Dominic Sweetman <dom@algor.co.uk>
Cc: Jun Sun <jsun@mvista.com>, Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: Interrupt handling....
Date: Wed, 4 Sep 2002 09:40:14 -0700	[thread overview]
Message-ID: <20020904094014.B5241@momenco.com> (raw)
In-Reply-To: <200209040953.KAA17466@mudchute.algor.co.uk>; from dom@algor.co.uk on Wed, Sep 04, 2002 at 10:53:55AM +0100

On Wed, Sep 04, 2002 at 10:53:55AM +0100, Dominic Sweetman wrote:
> 
> Matthew,
> 
> > Okay... I think I've got a problem that isn't covered by the usual
> > examples.
> 
> Possibly this is too simple an answer and is stuff you know quite well
> already...

Yeah, it is. See my response to Maciej's posting....

> > Which, as you can see, attempts to access address 0xfc00000c.
> 
> But that address is in the MIPS CPU's 'kseg2' region.  Addresses there
> are always translated by the TLB, and you haven't got an entry.

It's also the physical address.

And this is the heart of the problem.  I set up an ioremap, so I thought
that the TLB exception handler would fix this for me.  It looks like that
code won't do anything if the exception was generated from an interrupt...
Or am I reading it wrong?  I'm not an expert on the TLB code...

> You could read the book ("See MIPS Run")...

I read it quite some time ago.  My copy got very dog-eared before I had the
majority of the information committed to memory.  Nice book, BTW.

Matt

-- 
Matthew Dharm                              Work: mdharm@momenco.com
Senior Software Designer, Momentum Computer

  parent reply	other threads:[~2002-09-04 16:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D6E87EB.4010000@mvista.com>
2002-09-04  1:10 ` Interrupt handling Matthew Dharm
2002-09-04  9:53   ` Dominic Sweetman
2002-09-04 12:58     ` Maciej W. Rozycki
2002-09-04 16:36       ` Matthew Dharm
2002-09-04 20:08         ` Dominic Sweetman
2002-09-05  9:17           ` Maciej W. Rozycki
2002-09-04 16:40     ` Matthew Dharm [this message]
2002-09-04 17:02       ` Maciej W. Rozycki
2002-09-04 18:16         ` Matthew Dharm
2002-09-05  9:04           ` Maciej W. Rozycki
2002-09-05 16:25 Jon Burgess
  -- strict thread matches above, loose matches on Subject: below --
2003-10-16 13:16 Sanil K
2003-10-16 13:51 ` Richard B. Johnson
2003-10-16 19:55   ` Maciej Zenczykowski
2003-10-16 20:10     ` Richard B. Johnson
2003-10-16 18:53 ` George Anzinger
2003-10-16 19:08 ` Tom Zanussi
     [not found] <AANLkTim+7sKv+-pwPqMa5QhvuGRRQBUq+=nB8H7NEy7m@mail.gmail.com>
2011-02-15 10:46 ` Mulyadi Santosa
2011-02-15 12:20   ` Darshan Ghumare
2011-02-16  4:35     ` Darshan Ghumare
     [not found]       ` <AANLkTi=gGBf3fL9aXd5W--M7kerg9e5EDsJzXQ3wFa+b@mail.gmail.com>
2011-02-16  5:55         ` Darshan Ghumare
2011-02-16  8:54     ` Mulyadi Santosa
2011-02-16 14:50       ` Bruce Rowen
2011-02-17  4:49         ` Darshan Ghumare
2011-02-17 14:59           ` Bruce Rowen

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=20020904094014.B5241@momenco.com \
    --to=mdharm@momenco.com \
    --cc=dom@algor.co.uk \
    --cc=jsun@mvista.com \
    --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 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.