linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Maibaum <f.maibaum@web.de>
To: Tony Lindgren <tony@atomide.com>, john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, psavo@iki.fi, clepple@ghz.cc
Subject: Re: [PATCH] amd76x_pm on 2.6.0-test9 cleanup
Date: Wed, 05 Nov 2003 20:42:57 +0100	[thread overview]
Message-ID: <oprx6jpvyfwilrtr@smtp.web.de> (raw)
In-Reply-To: <20031104191504.GB1042@atomide.com>

On Tue, 4 Nov 2003 11:15:04 -0800, Tony Lindgren <tony@atomide.com> wrote:


> I've heard of timing problems if it's compiled in, but supposedly they 
> don't
> happen when loaded as module.

As of 2.4.22 they happen regardless of compiling the code as a module or 
statically



> So it looks like there are some dependencies to other drivers that need 
> to
> be sorted out, or amd76x_pm needs to be loaded after some other
> initializations.

In an older thread it was mentioned that the module should sync the TSCs 
to the bios clock, or at least between the processors when it wakes up.

regards

Felix

-- 
LINUX - because booting is for adding hardware!

      parent reply	other threads:[~2003-11-05 19:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04  0:22 [PATCH] amd76x_pm on 2.6.0-test9 cleanup Tony Lindgren
2003-11-04 18:41 ` john stultz
2003-11-04 19:15   ` Tony Lindgren
2003-11-04 19:44     ` Charles Lepple
2003-11-04 20:05       ` Tony Lindgren
2003-11-04 20:52         ` Charles Lepple
2003-11-04 22:38         ` Charles Lepple
2003-11-04 23:11           ` Tony Lindgren
2003-11-04 23:46             ` Pasi Savolainen
2003-11-04 20:21     ` Pasi Savolainen
2003-11-04 20:55       ` Tony Lindgren
2003-11-04 20:57         ` john stultz
2003-11-04 21:14           ` Tony Lindgren
2003-11-14 11:56         ` Pasi Savolainen
2003-11-04 21:01       ` Charles Lepple
2003-11-04 21:17         ` Tony Lindgren
2003-11-05 19:42     ` Felix Maibaum [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=oprx6jpvyfwilrtr@smtp.web.de \
    --to=f.maibaum@web.de \
    --cc=clepple@ghz.cc \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psavo@iki.fi \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).