If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Michael, the watermarking on all phoronix images is a disaster. Please update the image to be semitransparent (~30%) instead of solid and it would make sense to make it smaller size, or make it occupy a maximum of 20% of image proportionally. :/

This is because, for many images you post, the "water"mark very often overlaps over information.

Michael, the watermarking on all phoronix images is a disaster. Please update the image to be semitransparent (~30%) instead of solid and it would make sense to make it smaller size, or make it occupy a maximum of 20% of image proportionally. :/

This is because, for many images you post, the "water"mark very often overlaps over information.

That they are most likely on the decline, because the bulk of the code has been written. Support for an entire generation of cards requires a lot of code. Adding support (may be only pci-ids) and fixing bug is far smaller and less frequent commits?

Also isn't r300g nearly done now? Hasn't r300 classic and r600 classic been dropped now? Would also reduce the amount of commits.

That they are most likely on the decline, because the bulk of the code has been written. Support for an entire generation of cards requires a lot of code. Adding support (may be only pci-ids) and fixing bug is far smaller and less frequent commits?

Also isn't r300g nearly done now? Hasn't r300 classic and r600 classic been dropped now? Would also reduce the amount of commits.

I could be wrong of course.

That was my thought. Commit activity looked more or less like your normal standard distribution curve, which you'd expect to see in regards to driver activity over time.