Handling of driver protocol extensions in cvs

[Adam Jackson]

On Monday 23 January 2006 14:55, Philip Langdale wrote:
> Hi all,
>
> I'm in the process of putting together a protocol extension
> for the vmware driver and I wanted to ask what the intended
> practice for organising such code is? Should I create a proto
> module for the headers which the driver would then depend
> on, and then a lib module for the client side bindings, as
> if it was a fullscale extension? Or is there some other
> preferred mechanism?

There is no preferred mechanism atm.  Whatever makes your life easiest, I 
suppose, though in the long term I would like as few driver-specific 
extensions as possible.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20060130/263f6cae/attachment.pgp>