On Sat, Mar 16, 2013 at 6:13 PM, Myron Stowe wrote:
> On Thu, Mar 14, 2013 at 9:03 AM, Myron Stowe wrote:
>> On Wed, Mar 13, 2013 at 3:40 AM, Xiangliang Yu wrote:
>>> Hi, Bjorn
>>>
>> > Now, the situation is like this:
>> > I captured the PCIE trace with analyzer and found that 1st BE
On Thu, Mar 14, 2013 at 9:03 AM, Myron Stowe wrote:
> On Wed, Mar 13, 2013 at 3:40 AM, Xiangliang Yu wrote:
>> Hi, Bjorn
>>
>>> >> > Now, the situation is like this:
>>> >> > I captured the PCIE trace with analyzer and found that 1st BE is 0x
>>> >> > when
>>> >> > accessing IO port space. Bu
On Wed, Mar 13, 2013 at 3:40 AM, Xiangliang Yu wrote:
> Hi, Bjorn
>
>> >> > Now, the situation is like this:
>> >> > I captured the PCIE trace with analyzer and found that 1st BE is 0x
>> >> > when
>> >> > accessing IO port space. But 9125 spec has some limitation, and the BE
>> >> > must
>> >
On Wed, Mar 13, 2013 at 10:16 PM, Robert Hancock wrote:
> On 03/08/2013 09:18 PM, Myron Stowe wrote:
>>
>> On Thu, Mar 7, 2013 at 11:51 PM, Xiangliang Yu
>> wrote:
>>>
>>> Hi, Bjorn
>>>
>>> Fix system hang issue: if first accessed resource file of BAR0 ~
>>> BAR4, system will hang after e
On 03/08/2013 09:18 PM, Myron Stowe wrote:
On Thu, Mar 7, 2013 at 11:51 PM, Xiangliang Yu wrote:
Hi, Bjorn
Fix system hang issue: if first accessed resource file of BAR0 ~
BAR4, system will hang after executing lspci command
This needs more explanation. We've already read the BARs by the t
On Tue, Mar 12, 2013 at 3:22 AM, Xiangliang Yu wrote:
> Hi, Myron
>> > Now, the situation is like this:
>> > I captured the PCIE trace with analyzer and found that 1st BE is 0x
>> > when
>> > accessing IO port space. But 9125 spec has some limitation, and the BE
>> > must
>> > be
>> > 0x0100,
On Mon, Mar 11, 2013 at 3:15 AM, Xiangliang Yu wrote:
> Hi, Myron
>
>> >>> >> > Fix system hang issue: if first accessed resource file of BAR0 ~
>> >>> >> > BAR4, system will hang after executing lspci command
>> >
>> > Any question? Thanks!
>>
>> Googling and looking at the PCI IDs data base I se
On Sat, Mar 9, 2013 at 7:49 AM, Xiangliang Yu wrote:
> Hi, Bjorn
>
>>> >> > Fix system hang issue: if first accessed resource file of BAR0 ~
>>> >> > BAR4, system will hang after executing lspci command
>>> >>
>>> >> This needs more explanation. We've already read the BARs by the
>>> >> time head
Hi, Bjorn
>> >> > Fix system hang issue: if first accessed resource file of BAR0 ~
>> >> > BAR4, system will hang after executing lspci command
>> >>
>> >> This needs more explanation. We've already read the BARs by the
>> >> time header quirks are run, so apparently it's not just the mere
>>
On Thu, Mar 7, 2013 at 11:51 PM, Xiangliang Yu wrote:
> Hi, Bjorn
>
>> >> > Fix system hang issue: if first accessed resource file of BAR0 ~
>> >> > BAR4, system will hang after executing lspci command
>> >>
>> >> This needs more explanation. We've already read the BARs by the time
>> >> header q
On Thu, Mar 7, 2013 at 11:51 PM, Xiangliang Yu wrote:
> Hi, Bjorn
>
>> >> > Fix system hang issue: if first accessed resource file of BAR0 ~
>> >> > BAR4, system will hang after executing lspci command
>> >>
>> >> This needs more explanation. We've already read the BARs by the time
>> >> header q
Hi, Bjorn
> >> > Fix system hang issue: if first accessed resource file of BAR0 ~
> >> > BAR4, system will hang after executing lspci command
> >>
> >> This needs more explanation. We've already read the BARs by the time
> >> header quirks are run, so apparently it's not just the mere act of
> >>
On Thu, Mar 7, 2013 at 8:07 PM, Xiangliang Yu wrote:
> Hi, Bjorn
>
>> > Fix system hang issue: if first accessed resource file of BAR0 ~
>> > BAR4, system will hang after executing lspci command
>>
>> This needs more explanation. We've already read the BARs by the time
>> header quirks are run, s
Hi, Bjorn
> > Fix system hang issue: if first accessed resource file of BAR0 ~
> > BAR4, system will hang after executing lspci command
>
> This needs more explanation. We've already read the BARs by the time
> header quirks are run, so apparently it's not just the mere act of
> accessing a BAR
On Thu, Mar 7, 2013 at 7:29 AM, wrote:
> From: Xiangliang Yu
>
> Fix system hang issue: if first accessed resource file of BAR0 ~
> BAR4, system will hang after executing lspci command
This needs more explanation. We've already read the BARs by the time
header quirks are run, so apparently it'
15 matches
Mail list logo