From: "Mark Chambers" <markc@mail.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Calling PCI Autoconfig again
Date: Tue, 7 Mar 2006 12:22:07 -0500 [thread overview]
Message-ID: <005601c6420b$a99add50$6401a8c0@CHUCK2> (raw)
In-Reply-To: 84F54A3B-0B2A-45B5-968D-68266C6EDEDA@kernel.crashing.org
>
> On Mar 7, 2006, at 10:53 AM, Mark Chambers wrote:
>
>>> I'm dealing with this exact same situation and having a discussion
>>> on lkml regarding the proper way to do this. In your case, do
>>> you care what addresses the FPGA is assigned at?
>>> http://marc.theaimsgroup.com/?l=linux-kernel&m=114140791428032&w=2
>>
>> Why does the PCI device have to have a fixed address? And how do
>> you load an FPGA from user space - mmap?
>
> In my case it does because we have other devices (DSPs) that are hard
> coded to know where in PCI address space the FPGA is.
>
Ah, ok. So I'm guessing we're talking about DSP bus-master operations
where the DSP is putting out physical PCI space addresses that the
MMU can't help map. I've run into a similar problem where I'd like to
be able to have a DSP do CPM/BD-like operations from SDRAM, but
it's exceedingly difficult to get the physical address of user-space data.
Well, FWIW, seems to me that something like what Greg K-H referred to,
where you pre-reserve space in PCI land, and then put the device there
when it becomes available, is the way to go. Otherwise you have this
un-managed hole in PCI space allocation that might cause other problems
with true hot-swap PCI, or break with kernel revisions.
Mark
next prev parent reply other threads:[~2006-03-07 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 14:17 Calling PCI Autoconfig again Wyse, Chris
2006-03-07 16:26 ` Kumar Gala
2006-03-07 16:53 ` Mark Chambers
2006-03-07 16:59 ` Kumar Gala
2006-03-07 17:22 ` Mark Chambers [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-07 19:25 Wyse, Chris
2006-03-07 19:57 ` Kumar Gala
2006-03-07 13:49 Wyse, Chris
2006-03-06 21:34 Wyse, Chris
2006-03-07 4:32 ` David Hawkins
2006-03-07 15:48 ` Michael Richardson
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='005601c6420b$a99add50$6401a8c0@CHUCK2' \
--to=markc@mail.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.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).