Hi Simon,
On Mon, Jul 6, 2015 at 8:51 PM, Simon Glass wrote:
> Hi Bin,
>
> On 6 July 2015 at 02:12, Bin Meng wrote:
>> Hi Tom,
>>
>> On Wed, Jul 1, 2015 at 7:17 AM, Simon Glass wrote:
>>> Hi Bin,
>>>
>>> On 22 June 2015 at 21:45, Bin Meng wrote:
Currently PCI expansion ROM address is assi
Hi Bin,
On 6 July 2015 at 02:12, Bin Meng wrote:
> Hi Tom,
>
> On Wed, Jul 1, 2015 at 7:17 AM, Simon Glass wrote:
>> Hi Bin,
>>
>> On 22 June 2015 at 21:45, Bin Meng wrote:
>>> Currently PCI expansion ROM address is assigned by a call to
>>> pciauto_setup_rom() outside of the pci auto config pr
Hi Tom,
On Wed, Jul 1, 2015 at 7:17 AM, Simon Glass wrote:
> Hi Bin,
>
> On 22 June 2015 at 21:45, 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 devic
Hi Bin,
On 22 June 2015 at 21:45, 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 alread
Hi Tom,
On Tue, Jun 23, 2015 at 11:45 AM, 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 wa
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
6 matches
Mail list logo
