Hello,
On 2014-07-31 01:49, Grant Likely wrote:
On Tue, Jul 29, 2014 at 11:33 PM, Marek Szyprowski
wrote:
Hello,
On 2014-07-29 23:54, Grant Likely wrote:
On Mon, 14 Jul 2014 10:28:06 +0200, Marek Szyprowski
wrote:
Initialization procedure of dma coherent pool has been split into two
parts
On Tue, Jul 29, 2014 at 11:33 PM, Marek Szyprowski
wrote:
> Hello,
>
>
> On 2014-07-29 23:54, Grant Likely wrote:
>>
>> On Mon, 14 Jul 2014 10:28:06 +0200, Marek Szyprowski
>> wrote:
>>>
>>> Initialization procedure of dma coherent pool has been split into two
>>> parts, so memory pool can now be
Hello,
On 2014-07-29 23:54, Grant Likely wrote:
On Mon, 14 Jul 2014 10:28:06 +0200, Marek Szyprowski
wrote:
Initialization procedure of dma coherent pool has been split into two
parts, so memory pool can now be initialized without assigning to
particular struct device. Then initialized region
On Mon, 14 Jul 2014 10:28:06 +0200, Marek Szyprowski
wrote:
> Initialization procedure of dma coherent pool has been split into two
> parts, so memory pool can now be initialized without assigning to
> particular struct device. Then initialized region can be assigned to
> more than one struct dev
Initialization procedure of dma coherent pool has been split into two
parts, so memory pool can now be initialized without assigning to
particular struct device. Then initialized region can be assigned to
more than one struct device. To protect from concurent allocations from
different devices, a s
5 matches
Mail list logo