Hi Tom,
On Mon, Jun 22, 2015 at 2:16 AM, Tom Rini wrote:
> On Sun, Jun 21, 2015 at 03:21:49PM +0800, Bin Meng wrote:
>> +Tom since I see this patch was assigned to Tom in the patchwork.
>>
>> Hi Matt,
>>
>> On Sat, Jun 20, 2015 at 1:40 AM, Matt Porter wrote:
>> > On Fri, Jun 19, 2015 at 04:15:04
On Sun, Jun 21, 2015 at 03:21:49PM +0800, Bin Meng wrote:
> +Tom since I see this patch was assigned to Tom in the patchwork.
>
> Hi Matt,
>
> On Sat, Jun 20, 2015 at 1:40 AM, Matt Porter wrote:
> > On Fri, Jun 19, 2015 at 04:15:04PM +0800, Bin Meng wrote:
> >> Currently PCI expansion ROM addres
+Tom since I see this patch was assigned to Tom in the patchwork.
Hi Matt,
On Sat, Jun 20, 2015 at 1:40 AM, Matt Porter wrote:
> On Fri, Jun 19, 2015 at 04:15:04PM +0800, Bin Meng wrote:
>> Currently PCI expansion ROM address is assigned by a call to
>> pciauto_setup_rom() outside of the pci aut
On Fri, Jun 19, 2015 at 04:15:04PM +0800, Bin Meng wrote:
> Currently PCI expansion ROM address is assigned by a call to
> pciauto_setup_rom() outside of the pci auto config process.
> This does not work when expansion ROM is on a device behind
> PCI bridge where bridge's memory limit register was
Currently PCI expansion ROM address is assigned by a call to
pciauto_setup_rom() outside of the pci auto config process.
This does not work when expansion ROM is on a device behind
PCI bridge where bridge's memory limit register was already
programmed to a value that does not cover the newly assign
5 matches
Mail list logo