From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Deepak Pandian <peerlessdeepaks@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PCI Resource allocation
Date: Fri, 05 Dec 2008 09:54:04 +1100 [thread overview]
Message-ID: <1228431244.10722.4.camel@pasglop> (raw)
In-Reply-To: <cbaa36330812041036u751ea939qc0aea60002655d07@mail.gmail.com>
On Fri, 2008-12-05 at 00:06 +0530, Deepak Pandian wrote:
> Hi,
>
> In ppc4xx_pci i see the pci size to be declared as
> u32 lah, lal, pciah, pcial, sa;
I think the 4xx code is pretty much ok at this stage no ?
> Also at many other places I see the pci region is not capable of
> handling resources > 4GB. I am planning to work on this arch specific
> code to make it handle pci resource of width greater than 4 GB.
Which "many other places" ?
> But before that i wanted to clarify whether the core kernel will be
> able to handle pci regions with width greater than 4GB.
There's at least one place in the generic PCI code, in
pci_read_bridge_bases(), that needs fixing in a similar way as we
already fixed __pci_read_base(), ie by testing the resource_size_t size
rather than whether the platform is 64-bit.
There might be a few more.
Cheers,
Ben.
next prev parent reply other threads:[~2008-12-04 22:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 18:36 PCI Resource allocation Deepak Pandian
2008-12-04 22:54 ` Benjamin Herrenschmidt [this message]
2008-12-05 0:12 ` Flores, Raul
2008-12-07 23:00 ` Benjamin Herrenschmidt
2008-12-05 3:40 ` Deepak Pandian
-- strict thread matches above, loose matches on Subject: below --
2016-09-19 18:15 PCI Resource Allocation Robert Jones
2016-09-19 19:41 ` Bjorn Helgaas
2016-09-19 20:59 ` Robert Jones
2016-10-01 3:20 ` Yinghai Lu
2002-12-09 14:53 John Traill
2001-08-21 6:11 PCI resource allocation Jim McCloskey
2000-10-04 6:53 Michael Thompson
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=1228431244.10722.4.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=peerlessdeepaks@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.