Is there an easy way to support specific vendor formats in weston?

Hi weston contributors,

When integrate weston-13 on our own platform (with some vender specific changes), I found that by 903721a6 f49d6f47 , unknown formats (including our vendor specific formats) would be rejected when collecting supported formats of dmabuf protocol.

I wonder if that's reasonable to maintain a hard-coded table (pixel_format_table) in weston repo? For now, if we want to add specific formats, we need to change weston code to modify this table, which I suppose is not a good way.

Do you have any suggestions? Besides, during weston upgradation, we've observed multiple API/structure changes, which makes it difficult to integrate our vender-specific backend. Is there any guidelines/golden examples on how should vendors maintain their own backends to achieve a minimum effort when weston got upgraded?

Thanks, Sherry