[Libva] [RFC] Split <va/va.h>

[Bian, Jonathan]

I am not sure whether I'd go as far as splitting the header into so many pieces ... it seems that this would just make it more cumbersome for someone to go through the interfaces.  At least I would keep the core encode/decode interfaces in the same header file.

Regards,
Jonathan

-----Original Message-----
From: libva-bounces at lists.freedesktop.org [mailto:libva-bounces at lists.freedesktop.org] On Behalf Of Gwenole Beauchesne
Sent: Thursday, September 24, 2009 2:13 AM
To: libva at lists.freedesktop.org
Subject: [Libva] [RFC] Split <va/va.h>

Hi,

I now want to split <va/va.h> into smaller pieces. The goal is to ease 
access to the information (codec, image, etc.) and then improve 
documentation in the new files.

Users will still #include <va/va.h> -- no change is needed in their code.

The other rationale is to extend VA API to support other codecs from 3rd 
parties. I will make another mail for this one. ;-)

The planned changes:
- va_CODEC.h where CODEC is mpeg2, mpeg4, h264, vc1
- va_buffer.h: VABuffer related
- va_image.h: VAImage related
- va_subpic.h: VASubpicture related
- va_render.h: for vaBeginPicture() et al.

Since buffers and render functions are not optional decode paths, that 
probably still live in <va/va.h>. i.e. I am undecided yet for va_buffer.h 
and va_render.h files.

WDYT?

Regards,
Gwenole.
_______________________________________________
Libva mailing list
Libva at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libva