On Wednesday 05 March 2014, Liviu Dudau wrote:
> + unsigned long port = -1;
> + if (!pci_register_io_range(range->cpu_addr, range->size))
> + port = pci_address_to_pio(range->cpu_addr);
I don't remember the outcome of my suggestion to just return
On Wednesday 05 March 2014, Liviu Dudau wrote:
+ unsigned long port = -1;
+ if (!pci_register_io_range(range-cpu_addr, range-size))
+ port = pci_address_to_pio(range-cpu_addr);
I don't remember the outcome of my suggestion to just return 'port'
On Wed, 5 Mar 2014 11:48:53 +, Liviu Dudau wrote:
> The ranges property for a host bridge controller in DT describes
> the mapping between the PCI bus address and the CPU physical address.
> The resources framework however expects that the IO resources start
> at a pseudo "port" address 0
On Wed, 5 Mar 2014 11:48:53 +, Liviu Dudau liviu.du...@arm.com wrote:
The ranges property for a host bridge controller in DT describes
the mapping between the PCI bus address and the CPU physical address.
The resources framework however expects that the IO resources start
at a pseudo port
The ranges property for a host bridge controller in DT describes
the mapping between the PCI bus address and the CPU physical address.
The resources framework however expects that the IO resources start
at a pseudo "port" address 0 (zero) and have a maximum size of IO_SPACE_LIMIT.
The conversion
The ranges property for a host bridge controller in DT describes
the mapping between the PCI bus address and the CPU physical address.
The resources framework however expects that the IO resources start
at a pseudo port address 0 (zero) and have a maximum size of IO_SPACE_LIMIT.
The conversion
6 matches
Mail list logo