From: Matt Porter <mporter@mvista.com>
To: Neil Wilson <nwilson@airspan.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: forcing pci device start address ?
Date: Mon, 1 Apr 2002 13:35:35 -0700 [thread overview]
Message-ID: <20020401203535.GD20767@beef.az.mvista.com> (raw)
In-Reply-To: <000701c1d9ba$c2f27aa0$b3ff883e@m5axc>
On Mon, Apr 01, 2002 at 09:21:08PM +0100, Neil Wilson wrote:
> >Ok, I see the horrible mess they put you in. Those !@$!# hardware
> >guys. :-/
>
> >Here's the basic layout: you can use pci_auto like the other 7xx/74xx
> >embedded ports and constrain the I/O and Mem range so as to not conflict
> >with the PCI-wannabe devices your hardware guys spit out. You are
> >writing custom drivers so you just depart from the Linux standard of
> >ioremaping or in*/out*ing resources and use your hardcoded addresses.
>
> >You could complicate things by manually adding the devices to the
> >PCI global list and creating resources but there is no value in that
> >for a custom design like this...you could boast about it to your
> >fellow engineers if you like though. :)
>
>
> Thanks for your help, I will start looking at this when I get in tomorrow.
>
> Do you happen to know of a driver example in one of the kernel trees or
> elsewhere that implements this hardcoded address business that I can learn
> from ?
All you need to do is
ioremap(<hardcoded_base_address_in_physical_space>),<region_size>)
rather than ioremapping the PCI resource like a normal 2.3/2.4 PCI
device.
--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-01 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 20:21 forcing pci device start address ? Neil Wilson
2002-04-01 20:35 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-31 20:02 Neil Wilson
2002-04-01 4:04 ` Matt Porter
2002-03-30 17:14 Neil Wilson
2002-03-30 23:24 ` Matt Porter
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=20020401203535.GD20767@beef.az.mvista.com \
--to=mporter@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nwilson@airspan.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).