On Fri, Feb 22, 2013 at 2:31 PM, Verbeiren, David
wrote:
> On Wed, Feb 13, 2013 at 22:16, Blue Swirl wrote:
>>> +/* RGBA => NV12 */
>>> +for (i = 0; i < h264->pic_height; ++i) {
>>> +dst_y = (pdst + image.offsets[0]) + i*image.pitches[0];
>>> +dst_uv = dst_uv_line;
>>> +
On Wed, Feb 13, 2013 at 22:16, Blue Swirl wrote:
>> +/* RGBA => NV12 */
>> +for (i = 0; i < h264->pic_height; ++i) {
>> +dst_y = (pdst + image.offsets[0]) + i*image.pitches[0];
>> +dst_uv = dst_uv_line;
>> +s = psrc;
>> +for (j = 0; j < h264->pic_width; j++)
"Daniel P. Berrange" writes:
> On Wed, Feb 13, 2013 at 11:45:04AM +0100, David Verbeiren wrote:
>> This patch implements H.264 encoding of the VNC framebuffer updates
>> using hardware acceleration through the VA API.
>>
>> This is experimental support to let the community explore the possibilit
On Wed, Feb 13, 2013 at 11:45:04AM +0100, David Verbeiren wrote:
> This patch implements H.264 encoding of the VNC framebuffer updates
> using hardware acceleration through the VA API.
>
> This is experimental support to let the community explore the possibilities
> offered by the potential bandwi
On Wed, Feb 13, 2013 at 10:45 AM, David Verbeiren
wrote:
> This patch implements H.264 encoding of the VNC framebuffer updates
> using hardware acceleration through the VA API.
>
> This is experimental support to let the community explore the possibilities
> offered by the potential bandwidth and