From: Dan Malek <dan@mvista.com>
To: ashish anand <ashisha@india.infogain.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: placing of ioremap ?
Date: Tue, 01 May 2001 15:33:31 -0400 [thread overview]
Message-ID: <3AEF0F8B.836C77A7@mvista.com> (raw)
In-Reply-To: 12D7C6A4.AE725CC6@india.infogain.com
ashish anand wrote:
>
> 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
Well, you really shouldn't.......The PCI I/O space could be
done there so the usual inb/outb and friends work. PCI memory
space should not be mapped there, it is done by the driver.
> 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?
You should include the Linux PCI auto config function. It will
do this plus properly assign the interrupts.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-05-01 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 12:38 placing of ioremap ? ashish anand
2001-05-01 19:33 ` 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=3AEF0F8B.836C77A7@mvista.com \
--to=dan@mvista.com \
--cc=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).