linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: greg@kroah.com (Greg KH)
Cc: john@grabjohn.com (John Bradford),
	jgarzik@pobox.com (Jeff Garzik),
	alan@lxorguk.ukuu.org.uk (Alan Cox),
	mochel@osdl.org (Patrick Mochel),
	andrew.grover@intel.com (Grover Andrew),
	benh@kernel.crashing.org (Benjamin Herrenschmidt),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: Subtle semantic issue with sleep callbacks in drivers
Date: Fri, 18 Apr 2003 08:51:11 +0100 (BST)	[thread overview]
Message-ID: <200304180751.h3I7pBak000432@81-2-122-30.bradfords.org.uk> (raw)
In-Reply-To: <20030418073754.GA2753@kroah.com> from "Greg KH" at Apr 18, 2003 12:37:54 AM

> > > > > The video BIOS on a card often contains information that is found
> > > > > -nowhere- else.  Not in the chip docs.  Not in a device driver.
> > > > > Such information can and does vary from board-to-board, such as RAM
> > > > > timings, while the chip remains unchanged.
> > > > 
> > > > Incidently, what happens if we:
> > > > 
> > > > * Suspend
> > > > * Swap VGA card with another one
> > > > * Restore
> > > 
> > > When it breaks, you get to keep both pieces.
> > > 
> > > That's a "Don't Do That" issue for any hardware between suspend
> > > and resume.
> > 
> > Hmm, well what about with a PCI hotswap capable board - presumably
> > then we could have the situation where a new VGA card appears that we
> > _have_ to POST?
> 
> PCI Hotplug does not support video cards for just this reason.

Hmm, so is there no way at all we could support it?  I know it sounds
a bit pointless for a typical server or desktop machine, but it's
getting increasingly possible, practical, and attractive to use Linux
boxes more like minicomputers - dual headed VGA cards are cheap, and
USB allows you to connect practically as many keyboards and mice as
you want to.

I'm just thinking that at some point in the future, buying a new
machine could be less pratical than hot plugging in an additional VGA
card, keyboard, monitor and mouse, and editing a config file
somewhere.  With the new input layer, we are very close to this being
a reality.

John.

  reply	other threads:[~2003-04-18  7:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:07 Grover, Andrew
2003-04-14 19:18 ` Benjamin Herrenschmidt
2003-04-14 19:56 ` Alan Cox
2003-04-23 15:34 ` Pavel Machek
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=200304180751.h3I7pBak000432@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrew.grover@intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --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 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).