Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Clem Taylor <clem.taylor@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: troubles writing to a mmapped PCI BAR
Date: Fri, 22 Apr 2005 21:27:40 +0100	[thread overview]
Message-ID: <20050422202740.GY20252@linux-mips.org> (raw)
In-Reply-To: <ecb4efd105042213221c30cac4@mail.gmail.com>

On Fri, Apr 22, 2005 at 04:22:53PM -0400, Clem Taylor wrote:

> So I tried adding this before my io_remap_page_range() and it seems to
> have fixed my problem. My mmap() write to a PCI device is working now.
> I tried setting just the _PAGE_DIRTY bit and that seems to be the
> trick. Any ideas why I would need do to this or what is going on?

Without the process simply won't have access priviledges to that page, see
the TLB chapter of the CPU manual.

(I'm simplifying things alot here.)

  Ralf

      reply	other threads:[~2005-04-22 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 19:31 troubles writing to a mmapped PCI BAR Clem Taylor
2005-04-22 20:22 ` Clem Taylor
2005-04-22 20:27   ` Ralf Baechle [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=20050422202740.GY20252@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=clem.taylor@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox