linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Nico -telmich- Schottelius <nico-linux-next@schottelius.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Current suspend issues on Lenovo X200
Date: Sat, 25 Oct 2008 17:55:06 +0200	[thread overview]
Message-ID: <200810251755.11253.andres@anarazel.de> (raw)
In-Reply-To: <20081025145329.GB4273@denkbrett.schottelius.org>

[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]

Hi Nico,

On Saturday 25 October 2008 16:53:29 Nico -telmich- Schottelius wrote:
> Jesse Barnes [Fri, Oct 24, 2008 at 11:23:17AM -0700]:
> > On Friday, October 24, 2008 7:28 am Andres Freund wrote:
> > > On Thursday 23 October 2008 22:43:26 Nico -telmich- Schottelius wrote:
> > > >  - 2.6.27-next-20081023:
> > > >    -> no X running (because xorg does not work with that kernel)
> > > I think what you need is one rather short fix for the intel xorg
> > > driver:
> > > diff --git a/src/i830_driver.c b/src/i830_driver.c
> > > index c1d61f4..eaf5d27 100644
> > > --- a/src/i830_driver.c
> > > +++ b/src/i830_driver.c
> > > @@ -502,8 +502,8 @@ I830DetectMemory(ScrnInfoPtr pScrn)
> > >     range = gtt_size + 4;
> > >
> > >     /* new 4 series hardware has seperate GTT stolen with GFX stolen */
> > > - if (IS_G4X(pI830))
> > > - range = 0;
> > > + if (IS_G4X(pI830) || IS_GM45(pI830))
> > > + range = 4;
> > >
> > >     if (IS_I85X(pI830) || IS_I865G(pI830) || IS_I9XX(pI830)) {
> > >        switch (gmch_ctrl & I855_GMCH_GMS_MASK) {
> > >
> > > (Out of the "[git pull] agp patches for 2.6.28-rc1" thread)
> > Something like this might also help.
> > G4x chips do their own memory arbitration management, so we shouldn't
> > trying to save/restore the DSPARB reg.
> I'm a bit confused. Which of both patches against 2.6.28-rc1 should I try?
"My" patch is definitely needed to make the X intel driver work with 2.6.28-
rc1. Its a patch for X and not for the kernel.
Its not necessarily directly related to what you reported, but to:
> - 2.6.27-next-20081023:
>  -> no X running (because xorg does not work with that kernel)
It might also help to work with suspend, because seemingly (according to Intel 
people) its not expected that the driver works with that bug.

So try the patch I posted (which is out of the upstream development version) 
to make X work with 2.6.28-rc1 and continue testing if X works with 2.6.28-
rcx.

Andres

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2008-10-25 15:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 20:43 Current suspend issues on Lenovo X200 Nico -telmich- Schottelius
2008-10-23 21:07 ` Nico Schottelius
2008-10-23 22:06   ` Rafael J. Wysocki
2008-10-24  3:03     ` Nigel Cunningham
2008-10-24  7:11       ` Current suspend issues on Lenovo X200 (w/ Intel graphics) Rafael J. Wysocki
2008-10-24 13:01         ` Nico -telmich- Schottelius
2008-10-24 14:01           ` Mikael Abrahamsson
2008-10-24 14:30           ` Andres Freund
2008-10-24 18:02             ` Jens Axboe
2008-10-24 18:30               ` Rafael J. Wysocki
2008-10-24 18:47                 ` Jens Axboe
2008-10-24 18:56                   ` Rafael J. Wysocki
2008-10-24 18:55                     ` Jens Axboe
2008-10-24 19:05                       ` Rafael J. Wysocki
2008-10-24 18:50               ` Andres Freund
2008-10-24 18:26             ` Rafael J. Wysocki
2008-10-24 14:28 ` Current suspend issues on Lenovo X200 Andres Freund
2008-10-24 18:23   ` Jesse Barnes
2008-10-25 14:53     ` Nico -telmich- Schottelius
2008-10-25 15:55       ` Andres Freund [this message]

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=200810251755.11253.andres@anarazel.de \
    --to=andres@anarazel.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nico-linux-next@schottelius.org \
    /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;
as well as URLs for NNTP newsgroup(s).