linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: "svacca@valcom.com" <svacca@valcom.com>
Cc: "LinuxEmbeddedMailList (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Writing to PCI Bridge in User Space - Problem
Date: Mon, 17 Dec 2001 15:31:25 -0500	[thread overview]
Message-ID: <3C1E561D.1060005@embeddededge.com> (raw)
In-Reply-To: 01C18705.8C0C5810.svacca@valcom.com


Steven Vacca wrote:

> I have a "resident" driver which reads and writes a PLX PCI Bridge
> chip, which is mapped into 0x2000.0000 in MMU_init() (for the mpc860).

Bzzzzt!!  Potentially wrong answer.  How are you "mapping" it?  If you
are using ioremap(), this isn't going to work.  You either need to map it
much later in the kernel initialization, after the kernel VM is set up,
or by carefully choosing addresses for io_block_mapping().


> So, why does it work fine just before starting the app, from the non-driver
> kernel code, but not from the driver's ioctl fops func?

Because if you just use ioremap(), it placed the virtual address into the
user space.  When you started up the user programs the mapping was used for
it's intended purpose (user space).  There are plenty of messages in the
archives and FAQs describing the memory mapping.

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-12-17 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17 19:17 Writing to PCI Bridge in User Space - Problem Steven Vacca
2001-12-17 20:31 ` Dan Malek [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=3C1E561D.1060005@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=svacca@valcom.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;
as well as URLs for NNTP newsgroup(s).