From: Baoquan He
Date: Sun, 13 Nov 2016 13:01:31 +0800
> This is v2 post.
>
> In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
> firmware requesting code was moved from open stage to probe stage.
> The reason is in kdump kernel hardware iommu need device be reset in
> drive
On 11/14/16 18:28, David Miller wrote:
From: Paul Menzel
Date: Mon, 14 Nov 2016 09:25:47 +0100
On 11/13/16 06:01, Baoquan He wrote:
This is v2 post.
In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
firmware requesting code was moved from open stage to probe stage.
The
From: Paul Menzel
Date: Mon, 14 Nov 2016 09:25:47 +0100
> Dear Baoquan,
>
> On 11/13/16 06:01, Baoquan He wrote:
>> This is v2 post.
>>
>> In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
>> firmware requesting code was moved from open stage to probe stage.
>> The reason is
On 11/14/16 at 09:25am, Paul Menzel wrote:
> Dear Baoquan,
>
> On 11/13/16 06:01, Baoquan He wrote:
> > This is v2 post.
> >
> > In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
> > firmware requesting code was moved from open stage to probe stage.
> > The reason is in kdump
Dear Baoquan,
On 11/13/16 06:01, Baoquan He wrote:
This is v2 post.
In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
firmware requesting code was moved from open stage to probe stage.
The reason is in kdump kernel hardware iommu need device be reset in
driver probe stage,
This is v2 post.
In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
firmware requesting code was moved from open stage to probe stage.
The reason is in kdump kernel hardware iommu need device be reset in
driver probe stage, otherwise those in-flight DMA from 1st kernel
will con
