On Thu, Jun 16, 2011 at 1:21 AM, Chia-I Wu <olva...@gmail.com> wrote: > On Thu, Jun 16, 2011 at 7:04 AM, Marek Olšák <mar...@gmail.com> wrote: >> On Tue, Jun 14, 2011 at 10:35 PM, Benjamin Franzke >> <benjaminfran...@googlemail.com> wrote: >>> Removing this flag seems right to me, but always building the egl >>> state tracker when gallium and egl is enabled not. >>> So when --with-state-trackers is also removed, we'd need a new >>> --with-egl-drivers=auto|gallium,dri2,glx or so. >> >> Isn't --with-egl-platforms good enough to select among fbdev, wayland, >> one-day-maybe dri, ...? I don't see a reason for another option. You >> can choose between dri and xlib (st/glx) already using >> --with-driver=dri|xlib. > OpenGL can be supported via both egl_dri2 and egl_gallium EGL drivers. > The former is generally preferred for various reasons. However, when > both drivers exist, there is no automatic way to make EGL chooses the > former. Thus it is desirable to be able to disable egl_gallium in the > first place.
Why not to use egl_dri2 for all drivers, the classic and gallium ones? Why not to build a single fully-replaceable binary for a driver, like classic swrast_dri.so can be replaced by swrastg_dri.so from Gallium? Like radeon_drv.so from xf86-video-ati can be replaced by r300_drv.so from Gallium? I thought it had been agreed long ago that Gallium is a private unstable interface inside drivers and shouldn't be exposed publicly in any way. With that, I see no reason for egl_gallium.so to exist. Marek _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev