On Sun, Jan 23, 2011 at 1:35 PM, Ken Moffat <[email protected]> wrote: > On Sun, Jan 23, 2011 at 02:06:39PM -0600, Bruce Dubbs wrote: >> DJ Lucas wrote: >> >> > I am going to revert the changes for the configuration sections for now >> > and leave the old in place with an added note. As far as the Mesa demos, >> > the license is very permissive for at least the two we use. Not a big >> > deal at all to drop them and a small Makefile into the Mesa source tree >> > directly. Any objections to that, or is there some interest in the whole >> > demos package? Thus far, we've only ever installed glxgears and glxinfo. >> >> The whole demos package might be interesting, but whether it is included >> in the book or not depends on the complexity. If it's easy, I suggest >> adding it. >> > I'm more interested in how useful, or not, it turns out to be. > Maybe it's just my old hardware, but on the box with a radeon 7500 > I've built a full desktop with Mesa-7.9 and mesa-demos looks nice, > but glxgears is less than useful - it crashes if I try to move or > maximize its window. On that box, glxinfo works ok. Both multictx > and offset look nice, but no "mine's bigger than yours" numbers (and > in any case everything should now run at the screen's refresh rate > according to the glxgears text from 7.8.2). Other visual demos > report failed assertions in the radeon code. Xscreensaver works > fine.
This is why glxgears _is_ useful. It's an extremely simple 3d program that lets you know if your driver can actually put pixels on the screen. When a new driver is being developed for mesa, the "hey everybody I got this working" moment is usually when gears can run without crashing. Clearly your driver is broken if it's crashing. All glxinfo does is load the driver and check extensions and visuals. Very important info, but not the same as actually running anything. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
