From: Greg KH <greg@kroah.com>
To: David Vrabel <dvrabel@arcom.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] PCI: Add is_bridge to pci_dev to allow fixups to disable bridge functionality.
Date: Fri, 29 Oct 2004 20:23:57 -0700 [thread overview]
Message-ID: <20041030032357.GA1441@kroah.com> (raw)
In-Reply-To: <4174F909.1040804@arcom.com>
On Tue, Oct 19, 2004 at 12:22:49PM +0100, David Vrabel wrote:
> Hi,
>
> This patch allows device fixups to force the PCI subsystem to ignore
> bridges and hence not allocate resources to them.
>
> I have an IXP425 (ARM) board with a CardBus controller on it (of which
> only the PC card interfaces are used). The problem is that the PCI
> memory window is too small to fit in all the bridge resources and the
> rest of the PCI devices and up being unconfigured. With this patch, and
> a fixup to clear is_bridge, this doesn't happen.
>
> The plan was to make the CardBus driver (drivers/pcmcia/yenta_socket.c)
> honour the is_bridge flag and not bother with CardBus stuff if it's cleared.
But why can't any code that wants to check this, just look at the
dev->hdr_type instead? I don't think we need to add a new bit for this
because of that, right?
> Index: linux-2.6-armbe/drivers/pci/probe.c
> ===================================================================
> --- linux-2.6-armbe.orig/drivers/pci/probe.c 2004-10-14
> 11:26:38.000000000 +0100
> +++ linux-2.6-armbe/drivers/pci/probe.c 2004-10-19
> 12:00:00.000000000 +0100
Also, your patch was linewrapped :(
thanks,
greg k-h
next prev parent reply other threads:[~2004-10-30 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 11:22 David Vrabel
2004-10-30 3:23 ` Greg KH [this message]
2004-11-01 10:59 ` David Vrabel
2004-11-01 11:34 ` Russell King
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=20041030032357.GA1441@kroah.com \
--to=greg@kroah.com \
--cc=dvrabel@arcom.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome