[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTim2czZfsbGaG=K-=dV5hENgUOUhjBpWoa+mTjyb@mail.gmail.com>
Date: Mon, 7 Feb 2011 22:11:29 +0800
From: Jeff Chua <jeff.chua.linux@...il.com>
To: Takashi Iwai <tiwai@...e.de>
Cc: Chris Wilson <chris@...is-wilson.co.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>, Len Brown <lenb@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_
On Mon, Feb 7, 2011 at 9:38 PM, Jeff Chua <jeff.chua.linux@...il.com> wrote:
> On Mon, Feb 7, 2011 at 6:15 PM, Takashi Iwai <tiwai@...e.de> wrote:
>>> Thanks, that looks good. What about other files? Did you change
>>> (especially intel_drv.h) from Linus git tree?
>
> I will try again from a fresh build tonight.
>
>>> I'll also check later to be sure (now I have no machine for testing).
>> I don't see any problem with my machine (but running in 32bit).
>>
>> Are you sure that you are seeing the same CRTC? There are two active
>> CRTCs on Intel, and both are initialized and set up.
>
> I don't know about that. Even when I attempt to just the pointer
> directly as in "static void intel_crtc_reset(struct intel_crtc
> *intel_crtc)", it ended up getting a different value. Strange.
>
> intel_crtc ffff880239aa5800
> intel_crtc ffff880239aa5000
>
>
> I'm building everything fresh now.
Same issue encountered even after a fresh build.
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists