From: David Ashley <dash@xdr.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem w/driver writing to User Space
Date: Wed, 2 Jan 2002 22:05:58 -0800 [thread overview]
Message-ID: <200201030605.g0365wE00267@dave.home> (raw)
Didn't this come up before? I thought Dan or someone answered this very
question.
You do the ioremap in kernel space, so the resultant address can't be used
as an address to put_user. Just treat it as a pointer directly:
*(UINT32 *)(plxPtr+ PCI9054_EEPROM_CTRL_STAT) |= (1<<16); // turn on
*(UINT32 *)(plxPtr+ PCI9054_EEPROM_CTRL_STAT) &= ~(1<<16); //turn off
If it ever worked I would think it is just a fluke, maybe you're forcing
the user space to appear like the kernel space.
-Dave
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-01-03 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 6:05 David Ashley [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-02 17:55 Problem w/driver writing to User Space Steven Vacca
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=200201030605.g0365wE00267@dave.home \
--to=dash@xdr.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).