public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Add pci_assign_resource_fixed -- allow fixed address assignments
Date: Thu, 27 Apr 2006 17:17:58 -0700	[thread overview]
Message-ID: <20060428001758.GA18917@kroah.com> (raw)
In-Reply-To: <116674A8-64F4-4F49-8AAC-06C94159B3B3@kernel.crashing.org>

On Thu, Apr 27, 2006 at 07:12:14PM -0500, Kumar Gala wrote:
> 
> On Apr 27, 2006, at 5:34 PM, Andrew Morton wrote:
> 
> >Kumar Gala <galak@kernel.crashing.org> wrote:
> >>
> >>On some embedded systems the PCI address for hotplug devices are  
> >>not only
> >>known a priori but are required to be at a given PCI address for  
> >>other
> >>master in the system to be able to access.
> >>
> >>An example of such a system would be an FPGA which is setup from  
> >>user space
> >>after the system has booted.  The FPGA may be access by DSPs in  
> >>the system
> >>and those DSPs expect the FPGA at a fixed PCI address.
> >>
> >>Added pci_assign_resource_fixed() as a way to allow assignment of  
> >>the PCI
> >>devices's BARs at fixed PCI addresses.
> >
> >Is there any sane way in which we can arrange for this function to  
> >not be
> >present in vmlinux's which don't need it?
> >
> >Options would be
> >
> >a) Put it in a .a file.
> >
> >   - messy from a source perspective
> >
> >   - doesn't work if the only reference is from a module
> >
> >   - small gains anyway.
> >
> >b) Use CONFIG_EMBEDDED.
> 
> I'm fine with wrapping it in a CONFIG_EMBEDDED, Greg?

That's fine with me.  Care to send me an updated patch?  I'll drop the
other one then.

thanks,

greg k-h

  reply	other threads:[~2006-04-28  0:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 17:43 [PATCH] PCI: Add pci_assign_resource_fixed -- allow fixed address assignments Kumar Gala
2006-04-27 22:34 ` Andrew Morton
2006-04-28  0:12   ` Kumar Gala
2006-04-28  0:17     ` Greg KH [this message]
2006-04-28  4:29       ` [PATCH][UPDATE] " Kumar Gala
2006-04-28  4:43         ` Andrew Morton
2006-04-28 14:52           ` Kumar Gala
2006-05-01 15:43             ` Kumar Gala
2006-05-02 13:13         ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-03-10 15:06 [PATCH] " Kumar Gala
2006-03-10 21:04 ` Randy.Dunlap
2006-03-10 21:30   ` Kumar Gala
2006-03-20 16:09     ` Kumar Gala
2006-03-28 16:26       ` Kumar Gala

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=20060428001758.GA18917@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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