Comment 262 for bug 252094

I also agree, but there is nothing we can do, this bug report is just a
place to complain.

Some time ago (probably a year ago), someone or a group of people at intel
driver development, decided that they will throw away legacy driver code
(that was performing without so much user complaints as the current
releases) while they rewrote it. They thought is was a good idea. They were
too much confident they would fix it quickly enough before everybody
noticed... but they were wrong.

They should have done as you allways do this things, that is:

   1. You maintain the old stuff while you write the new driver.
   2. When the new driver is stable (and currently IT ISN'T!) then you
   change the defaults to point to the new driver and leave the old one as a
   fallback.
   3. Later, when the old stuff is no longer mainstream or obsolete and the
   new stuff is rock-solid, then, and only then, you get rid of the old stuff
   and leave the new code alone.

I know it is painful (as a developer I really know it is) and it may sound
old-fashion, but it is more practical in the end.

But they decided to take the risk, and as Murphy law states, "what could go
wrong went wrong". We may have drivers performing decently again in 2011 or
so, (by the time Google Chrome Linux will be delivered) in the meantime we
can just complain or... if you know graphics development, retro-backport the
old TTM code (or whatever it was called) in new kernel and distro
releases... it will probably take less time to do than fixing current GEM
drivers.

2009/1/12 jspudz <email address hidden>

> I agree with Snover. This issue is more then just "some" people
> experiencing problems.....its everyone with an intel card. Like he said
> throw a stone and you will hit it.
>
> What exactly do you need, if not glxgears then tell us what. There are
> plenty of people with intel cards that are willing to provide the input
> you need including me but at this point we need to know what.
>
> The thing we all need to get at this point is its broke for all intel
> cards. Dont get mad because everyone with an intel card is reporting
> here because its broke. It's not their fault a release broke intel
> support. I see no point in starting multiple threads on this, as it
> will just turn out to be multiple threads saying the same thing this one
> is.
>
> --
> [i965, etc.] Poor graphics performance on Intel
> https://bugs.launchpad.net/bugs/252094
> You received this bug notification because you are a direct subscriber
> of the bug.
>