All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Patrick Mochel <mochel@osdl.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Subtle semantic issue with sleep callbacks in drivers
Date: Wed, 23 Apr 2003 17:34:41 +0200	[thread overview]
Message-ID: <20030423153441.GD3035@elf.ucw.cz> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A261@orsmsx401.jf.intel.com>

Hi!

> > What I mean here is that none of our drivers know how to bring 
> > back a chip as complicated as a radeon or a nvidia up from 
> > power off, this requires intimate knowledge of the chip 
> > internals, the way it's wired on a given board, etc...
> 
> All I am saying is that on Windows, the driver gets no help from the
> BIOS, APM, or ACPI, but yet it restores the video to full working
> condition. I understand that this sounds complicated, but since
> there is

It is not only complicated, we also lack docs neccessary to do that...

								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  parent reply	other threads:[~2003-04-23 15:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 19:07 Subtle semantic issue with sleep callbacks in drivers Grover, Andrew
2003-04-14 19:18 ` Benjamin Herrenschmidt
2003-04-14 19:56 ` Alan Cox
2003-04-14 21:07   ` Kernel Sockets Programming: closing sockets? Lamont Granquist
2003-04-23 15:34 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 21:09 Subtle semantic issue with sleep callbacks in drivers Grover, Andrew
2003-04-16 18:39 ` Patrick Mochel
2003-04-16 19:36   ` Benjamin Herrenschmidt
2003-04-17 13:35   ` Alan Cox
2003-04-17 14:48     ` Jeff Garzik
2003-04-17 15:09       ` John Bradford
2003-04-17 15:09         ` Jeff Garzik
2003-04-17 15:47           ` John Bradford
2003-04-17 15:56             ` Jeff Garzik
2003-04-17 16:24               ` Alan Cox
2003-04-18  7:37             ` Greg KH
2003-04-18  7:51               ` John Bradford
2003-04-18  9:10               ` Russell King
2003-04-18 11:18                 ` Alan Cox
2003-04-18 11:30               ` Alan Cox
2003-04-29  8:28         ` Pavel Machek
2003-04-17 14:59     ` John Bradford
2003-04-17 15:04       ` Alan Cox
2003-04-14 17:09 Grover, Andrew
2003-04-14 17:40 ` Benjamin Herrenschmidt
2003-04-23 15:29 ` Pavel Machek
2003-04-14 10:00 Benjamin Herrenschmidt
2003-04-14 10:11 ` Benjamin Herrenschmidt
2003-04-16 18:31 ` Patrick Mochel
2003-04-16 19:29   ` Benjamin Herrenschmidt
2003-04-23 15:32 ` 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=20030423153441.GD3035@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=andrew.grover@intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.