Re: [Mesa3d-dev] gallium "raw" interfaces

[Corbin S. <mos...@gm...>]

On Sun, Mar 28, 2010 at 12:19 PM, Luca Barbieri <luc...@gm...> wrote:
> I posted something similar some time ago, that however could use
> hardware accelerated drivers with DRI2 or KMS, provided a substantial
> set of helpers and offered a complement of 3 demos.
>
> My solution to window-system issues was to simply have the application
> provide a "draw" callback to the framework, which would automatically
> create a maximized window with the application name in the title, and
> call draw in a loop, presenting the results.
>
> Then I had a path that woud use the X DRI2 interface if possible, and
> another path that would use the Linux DRM KMS API (and initially some
> EGL+ad-hoc extension paths that were later dropped).
>
> It no longer works due to Gallium interface changes, but maybe it can
> be resurrected and merged with graw.
>
> However, there is a disadvantage to having Gallium programs in-tree:
> they break every time the Gallium interface in changed and avoiding
> that means that in addition to fixing all drivers and state trackers,
> you also need to fix all programs for each change

Presumably this will no longer be a problem when Gallium is a more
mature, stable interface. I much prefer this "try it and see"
mentality over the design-by-committee mess that has popped up
elsewhere.

--
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
<Mos...@gm...>