mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: airlied@linux.ie, linux-kernel@vger.kernel.org,
	ykzhao <yakui.zhao@intel.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Regression DRM/i915/KMS: VGA connector unusable after 2.6.31-rc8-git1, DVI connector ok
Date: Wed, 9 Sep 2009 07:28:28 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0909090719070.7458@localhost.localdomain> (raw)
In-Reply-To: <4AA7549B.5040905@t-online.de>



On Wed, 9 Sep 2009, Knut Petersen wrote:
> 
> As the old X does not work with the new kernel, I cannot decide if the 
> kernel or X is to blame.

Hmm. Doesn't old X work if you disable KMS? Either with "i915.modeset=0" 
or by just compiling it out?

Also, glxgears is usually not a good way to verify anything. At least some 
versions used to run the gears at the painting frame rate rather than some 
fixed rate, and so "jerky" or not depended not on how fast it was 
painting, but on whether the painting speed was some multiple of the 
screen refresh.

The FPS output from glxgears should mean something, although quite 
frankly, considering the simplicity of the thing, not a whole lot. I'd 
suggest using some somewhat more real test (I admit to having used 
"Extreme Tux Racer", which while not wonderful either is certainly better 
than glxgears ;^)

		Linus

  reply	other threads:[~2009-09-09 14:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 22:19 Knut Petersen
2009-09-08 22:26 ` Jesse Barnes
2009-09-09  1:05   ` [Intel-gfx] " ykzhao
2009-09-08 22:28 ` Carlos R. Mafra
2009-09-08 23:00   ` Knut Petersen
2009-09-08 23:11 ` Linus Torvalds
2009-09-09  7:09   ` Knut Petersen
2009-09-09 14:28     ` Linus Torvalds [this message]
2009-09-09 21:35       ` Knut Petersen
2009-09-09 16:04     ` Jesse Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.01.0909090719070.7458@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=Knut_Petersen@t-online.de \
    --cc=airlied@linux.ie \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yakui.zhao@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome