From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: gopi krishna <mgopik@yahoo.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Unable to read/write consistently to a device.
Date: Tue, 27 Feb 2001 20:27:29 +0100 [thread overview]
Message-ID: <19350122125913.1459@smtp.wanadoo.fr> (raw)
In-Reply-To: <20010227170238.55737.qmail@web11103.mail.yahoo.com>
> We have a device 0xf0040000. This address has been
>ioremapped.
>(Hence directly using the physical address to access
>the memory)
What do you mean by ioremapped ? You should use the virtual address
returned by ioremap (which is usually _not_ the same as the physical
address, except in some specific cases), not the physical address, to
access the registers.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-27 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 17:02 Unable to read/write consistently to a device gopi krishna
2001-02-27 19:27 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 17:10 gopi krishna
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=19350122125913.1459@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mgopik@yahoo.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).