linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev-devel@lists.sourceforge.net,
	"Antonino A. Daplas" <adaplas@pol.net>
Cc: william.pan@kontron.cn, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 9006] New: incorrect method to turn off DPLL in intel framebuffer driver
Date: Tue, 11 Sep 2007 00:49:41 -0700	[thread overview]
Message-ID: <20070911004941.28b1332f.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9006-10286@http.bugzilla.kernel.org/>

On Tue, 11 Sep 2007 00:40:22 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=9006
> 
>            Summary: incorrect method to turn off DPLL in intel framebuffer
>                     driver
>            Product: Platform Specific/Hardware
>            Version: 2.5
>      KernelVersion: 2.6.18.1
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: i386
>         AssignedTo: platform_i386@kernel-bugs.osdl.org
>         ReportedBy: william.pan@kontron.cn
> 
> 
> in file intelfbhw.c, function intelfbhw_program_mode, the steps to 
> turn off DPLL:
>         tmp = INREG(dpll_reg);
>         dpll_reg &= ~DPLL_VCO_ENABLE;
>         OUTREG(dpll_reg, tmp);
> guess it should be:
>         tmp = INREG(dpll_reg);
>         tmp &= ~DPLL_VCO_ENABLE;
>         OUTREG(dpll_reg, tmp);
> am I right?
> 

?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

           reply	other threads:[~2007-09-11  7:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-9006-10286@http.bugzilla.kernel.org/>]

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=20070911004941.28b1332f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adaplas@pol.net \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=william.pan@kontron.cn \
    /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).