> I was thinking it would be nice to color code it even more and add a legend > to distinguish at least the following states: > > +----------------------------+ > given a | the chip has hw support | > feature: +--------------+-------------+ > | Y | N | > -----------+----+----+----+------+------+ > the driver | hw | sw | no | sw | no | > supports | | | | | | > -----------+----+----+----+------+------+ > case 1 2 3 4 5 > Perhaps: > 1 green --nothing else to be done, and optimal > 2 pink or yellow --indicate work to be done > 3 yellow or red --indicate work to be done > 4 light green --nothing else can be done, but not as good as hw > 5 white? --indicate no work can be/to be done? >
Who is the audience for the table? Is it the end user checking to see if a feature is available and/or has some form of HW acceleration? Or is the audience the DRI developer, looking to see what pieces need implementing? That might dictate how much you put in the table, especially color coding. Nice looking table, I like it. Suzy ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
