Summary: | mesa builds drivers for r300 and Intel even when not asked to | ||
---|---|---|---|
Product: | Mesa | Reporter: | Michal Suchanek <hramrach> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Michal Suchanek
2010-10-12 03:02:46 UTC
Specifically I have no idea why I have some i915 and r300 drivers when I asked to build r600 only. Gallium/r300 is built by default. You can disable it with the parameter --disable-gallium-radeon. There are other drivers and libs built by default, like Gallium/swrast, egl, glu. Gallium/i915 is not actually built, only the source files are compiled for us to have everything compile-tested. I can understand building swrast by default. It's useful to some extent on any hardware. However, r300 on a r600 card is completely useless. At least now the r300g driver is actually installed when it is built. Thanks Michal The way I understand it is that when you type make && sudo make install, you should get all stable drivers installed. You disabled classic r300 by setting --with-dri-drivers=r600 (otherwise classic r300 would be built), selecting only classic r600 with that option (so you build both classic and gallium r600, why?). The Gallium drivers are only selected or deselected using --enable-gallium-something or --disable-gallium-something, respectively, and there are some default enables, as you noticed. The selected Gallium drivers are listed in "Target dirs", the other "dirs" are usually just some internal dependencies you don't have to care about. Of course, what should or should not be built by default may be revisited sometime. I am closing this as it's not a bug. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.