public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan@hell.org.pl>
To: Terence Ripperda <tripperda@nvidia.com>
Cc: Stefan Seyfried <seife@gmane0305.slipkontur.de>,
	swsusp-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Pavel Machek <pavel@suse.cz>
Subject: Re: [Swsusp-devel] Re: nvidia's driver and swsusp (need help w/ n forc e2 mobo)
Date: Sat, 3 Jul 2004 01:22:28 +0200	[thread overview]
Message-ID: <20040702232228.GA19080@hell.org.pl> (raw)
In-Reply-To: <20040702200012.GU1815@hygelac>

Thus wrote Terence Ripperda:
> I tried hibernating/resuming while in X. but I don't see any acpi
> calls coming through to our driver via the pci driver model. is this
> expected?

I'm no PM expert, but I'm getting the idea that you're wrong at your
principles. 

To begin with, there's no such thing as acpi calls. There's driver model in
2.6 (i.e. pci_module_init() / pci_register_driver()), and there's 2.4's
lack of thereof (i.e. pm_register()). As far as I know, those two
interfaces have nothing specifically to do with ACPI nor APM. 

I think the proper way to conditionalize this in the code is to check for
CONFIG_PM as the prerequisite and KERNEL_2_6/!KERNEL_2_6 to choose between
those interfaces (and only that: bear in mind swsusp2 and pmdisk require
neither APM nor ACPI). Perhaps you're building with only CONFIG_PM defined?

Hopefully others will be able to clarify this.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan@hell.org.pl

       reply	other threads:[~2004-07-02 23:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040702192044.GO1815@hygelac>
     [not found] ` <20040702200012.GU1815@hygelac>
2004-07-02 23:22   ` Karol Kozimor [this message]
2004-07-03  0:35     ` [Swsusp-devel] Re: nvidia's driver and swsusp (need help w/ n forc e2 mobo) Pavel Machek

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=20040702232228.GA19080@hell.org.pl \
    --to=sziwan@hell.org.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=seife@gmane0305.slipkontur.de \
    --cc=swsusp-devel@lists.sourceforge.net \
    --cc=tripperda@nvidia.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