On Mon, Aug 6, 2012 at 6:52 AM, Daniel Vetter wrote:
> On Mon, Jul 30, 2012 at 02:06:54PM +1000, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> In order for udl vmap to work properly, we need to push the object
>> into the CPU domain before we start copying the data to the USB device.
>>
>> questi
On Mon, Aug 6, 2012 at 6:52 AM, Daniel Vetter wrote:
> On Mon, Jul 30, 2012 at 02:06:54PM +1000, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> In order for udl vmap to work properly, we need to push the object
>> into the CPU domain before we start copying the data to the USB device.
>>
>> questi
On Mon, Jul 30, 2012 at 02:06:54PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> In order for udl vmap to work properly, we need to push the object
> into the CPU domain before we start copying the data to the USB device.
>
> question: what is direction here in terms of read/write to the dev
On Mon, Jul 30, 2012 at 02:06:54PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> In order for udl vmap to work properly, we need to push the object
> into the CPU domain before we start copying the data to the USB device.
>
> question: what is direction here in terms of read/write to the dev
From: Dave Airlie
In order for udl vmap to work properly, we need to push the object
into the CPU domain before we start copying the data to the USB device.
question: what is direction here in terms of read/write to the device.
This along with the udl change avoids userspace explicit mapping to
From: Dave Airlie
In order for udl vmap to work properly, we need to push the object
into the CPU domain before we start copying the data to the USB device.
question: what is direction here in terms of read/write to the device.
This along with the udl change avoids userspace explicit mapping to