Hi Marcin,
On mar., nov. 29 2016, Marcin Wojtas wrote:
> Gregory,
>
> 2016-11-29 11:19 GMT+01:00 Gregory CLEMENT
> :
>> Hi Marcin,
>>
>> On mar., nov. 29 2016, Marcin Wojtas wrote:
>>
>>> Hi Gregory,
>>>
>>> Another
Hi Marcin,
On mar., nov. 29 2016, Marcin Wojtas wrote:
> Gregory,
>
> 2016-11-29 11:19 GMT+01:00 Gregory CLEMENT
> :
>> Hi Marcin,
>>
>> On mar., nov. 29 2016, Marcin Wojtas wrote:
>>
>>> Hi Gregory,
>>>
>>> Another remark below, sorry for noise.
>>>
>>> 2016-11-29 10:37 GMT+01:00 Gregory
Gregory,
2016-11-29 11:19 GMT+01:00 Gregory CLEMENT :
> Hi Marcin,
>
> On mar., nov. 29 2016, Marcin Wojtas wrote:
>
>> Hi Gregory,
>>
>> Another remark below, sorry for noise.
>>
>> 2016-11-29 10:37 GMT+01:00 Gregory CLEMENT
>>
Gregory,
2016-11-29 11:19 GMT+01:00 Gregory CLEMENT :
> Hi Marcin,
>
> On mar., nov. 29 2016, Marcin Wojtas wrote:
>
>> Hi Gregory,
>>
>> Another remark below, sorry for noise.
>>
>> 2016-11-29 10:37 GMT+01:00 Gregory CLEMENT
>> :
>>> Until now the virtual address of the received buffer were
Hi Marcin,
On mar., nov. 29 2016, Marcin Wojtas wrote:
> Hi Gregory,
>
> Another remark below, sorry for noise.
>
> 2016-11-29 10:37 GMT+01:00 Gregory CLEMENT
> :
>> Until now the virtual address of the received buffer were stored in the
Hi Marcin,
On mar., nov. 29 2016, Marcin Wojtas wrote:
> Hi Gregory,
>
> Another remark below, sorry for noise.
>
> 2016-11-29 10:37 GMT+01:00 Gregory CLEMENT
> :
>> Until now the virtual address of the received buffer were stored in the
>> cookie field of the rx descriptor. However, this
Hi Marcin,
On mar., nov. 29 2016, Marcin Wojtas wrote:
> Hi Gregory,
>
> Apparently HWBM had a mistake in implementation, please see below.
>
> 2016-11-29 10:37 GMT+01:00 Gregory CLEMENT
> :
>> Until now the virtual address of the
Hi Marcin,
On mar., nov. 29 2016, Marcin Wojtas wrote:
> Hi Gregory,
>
> Apparently HWBM had a mistake in implementation, please see below.
>
> 2016-11-29 10:37 GMT+01:00 Gregory CLEMENT
> :
>> Until now the virtual address of the received buffer were stored in the
>> cookie field of the rx
Hi Gregory,
Another remark below, sorry for noise.
2016-11-29 10:37 GMT+01:00 Gregory CLEMENT :
> Until now the virtual address of the received buffer were stored in the
> cookie field of the rx descriptor. However, this field is 32-bits only
> which prevents
Hi Gregory,
Another remark below, sorry for noise.
2016-11-29 10:37 GMT+01:00 Gregory CLEMENT :
> Until now the virtual address of the received buffer were stored in the
> cookie field of the rx descriptor. However, this field is 32-bits only
> which prevents to use the driver on a 64-bits
Hi Gregory,
Apparently HWBM had a mistake in implementation, please see below.
2016-11-29 10:37 GMT+01:00 Gregory CLEMENT :
> Until now the virtual address of the received buffer were stored in the
> cookie field of the rx descriptor. However, this field is
Hi Gregory,
Apparently HWBM had a mistake in implementation, please see below.
2016-11-29 10:37 GMT+01:00 Gregory CLEMENT :
> Until now the virtual address of the received buffer were stored in the
> cookie field of the rx descriptor. However, this field is 32-bits only
> which prevents to use
Until now the virtual address of the received buffer were stored in the
cookie field of the rx descriptor. However, this field is 32-bits only
which prevents to use the driver on a 64-bits architecture.
With this patch the virtual address is stored in an array not shared with
the hardware (no
Until now the virtual address of the received buffer were stored in the
cookie field of the rx descriptor. However, this field is 32-bits only
which prevents to use the driver on a 64-bits architecture.
With this patch the virtual address is stored in an array not shared with
the hardware (no
14 matches
Mail list logo