From: ashish anand <ashisha@india.infogain.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: placing of ioremap ?
Date: Tue, 01 May 2001 18:08:35 +0530 [thread overview]
Message-ID: <12D7C6A4.AE725CC6@india.infogain.com> (raw)
I have one question regarding the placing of ioremap call
suppose i have done ioremap call inside the mm/init.c
for pci i/o or memory space ..and if this space is above
the ioremap_base i would be having the virtual address
equal to physical address
now i don't need to call ioremap inside the driver code
since the resources (either pci i/o or memory or both) that
i am supposed to give a particular card has already been
ioremapped by now
in case my bios has not done the resource allocation
i have to just write the proper values in PCI_BASE_ADDRESS
registers of that pci card. Am I Correct?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-05-01 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 12:38 ashish anand [this message]
2001-05-01 19:33 ` placing of ioremap ? Dan Malek
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=12D7C6A4.AE725CC6@india.infogain.com \
--to=ashisha@india.infogain.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).