Hi,
i'm porting the linux 2.6.27 kernel to the custom board with PowerPC 7448 &
Marvell 64560. In DTS file the PCI ranges are configured as follows:
system-control...@fbe0 { /* Marvell Discovery mv64560 (Discovery
V)*/
#address-cells = <1>;
#size-cell
On Thu, 2008-12-04 at 18:12 -0600, Flores, Raul wrote:
> A bit off topic, but since the subject is pci resource allocation:
>
> As entered here:
> http://bugs.gentoo.org/show_bug.cgi?id=249832
>
> the 2.6.24-gentoo-r3 kernel; iomem tree for my video display works, but
>
Hi Ben,
On Fri, Dec 5, 2008 at 4:24 AM, Benjamin Herrenschmidt
<[EMAIL PROTECTED]> wrote:
> 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 thi
A bit off topic, but since the subject is pci resource allocation:
As entered here:
http://bugs.gentoo.org/show_bug.cgi?id=249832
the 2.6.24-gentoo-r3 kernel; iomem tree for my video display works, but
has not worked in the following kernels:
2.6.26-gentoo-r2
2.6.27-gentoo-r2
2.6.28-rc4
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 resourc
Hi,
In ppc4xx_pci i see the pci size to be declared as
u32 lah, lal, pciah, pcial, sa;
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.
But befor
The 32 bits PCI code now uses the generic code for assigning unassigned
resources and an algorithm similar to x86 for claiming existing ones.
This works far better than the 64 bits code which basically can only
claim existing ones (pci_probe_only=1) or would fall appart completely.
This merges th
The 32 bits PCI code now uses the generic code for assigning unassigned
resources and an algorithm similar to x86 for claiming existing ones.
This works far better than the 64 bits code which basically can only
claim existing ones (pci_probe_only=1) or would fall appart completely.
This merges th
The 32 bits PCI code now uses the generic code for assigning unassigned
resources and an algorithm similar to x86 for claiming existing ones.
This works far better than the 64 bits code which basically can only
claim existing ones (pci_probe_only=1) or would fall appart completely.
This merges th
The 32 bits PCI code now uses the generic code for assigning unassigned
resources and an algorithm similar to x86 for claiming existing ones.
This works far better than the 64 bits code which basically can only
claim existing ones (pci_probe_only=1) or would fall appart completely.
This merges th
10 matches
Mail list logo