public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Andres Salomon <dilinger@mp3revolution.net>,
	Marcus Meissner <Marcus.Meissner@caldera.de>,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH: trident , pci_enable_device moved
Date: 27 Apr 2001 03:33:41 -0600	[thread overview]
Message-ID: <m1pudyr8ju.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20010425090438.A12672@caldera.de> <20010425130624.A3216@caldera.de> <20010425104949.A31649@mp3revolution.net> <3AE6E797.A31803BE@mandrakesoft.com> <20010425112402.A31842@mp3revolution.net> <3AE6EEBF.D8A434D1@mandrakesoft.com>
In-Reply-To: Jeff Garzik's message of "Wed, 25 Apr 2001 11:35:27 -0400"

Jeff Garzik <jgarzik@mandrakesoft.com> writes:

> Andres Salomon wrote:
> > This is what I was told (it was only needed for secondary video
> > devices).  From that, I would expect that all video devices would
> > need it, just in case they happened to be the second card.  Am I
> > missing some subtlety in some of the video driers/chipsets that
> > wouldn't allow them to be used as a second video device (therefore
> > not requiring pci_enable_device)?
> 
> They do need pci_enable_device, both primary and secondary displays. 
> For the primary display its safe to call pci_enable_device.  For
> secondary displays, you have to first disable I/O decoding for all VGA
> devices before you can enable a secondary display.  You don't want more
> than one device decoding the legacy VGA region at any one time.
> 
> Some cards have the capability to relocate the VGA region, which is
> nice.  The bigger problem is initializing secondary displays; every
> video card has a proprietary video BIOS initialization sequence that is
> run by main BIOS on startup.  You can either duplicate this sequence
> with C code, which is sometimes difficult due to lack of docs or variety
> of boards, or you can execute the video BIOS with an x86 emulator.

Note:  With linuxBIOS (and some other embedded linux setups) even a
primary display doesn't get initialized until you start linux so if
you can properly initialize your display please do it.

Eric

      reply	other threads:[~2001-04-27  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-25  7:04 PATCH: trident , pci_enable_device moved Marcus Meissner
2001-04-25 11:06 ` Marcus Meissner
2001-04-25 14:49   ` Andres Salomon
2001-04-25 15:04     ` Jeff Garzik
2001-04-25 15:24       ` Andres Salomon
2001-04-25 15:35         ` Jeff Garzik
2001-04-27  9:33           ` Eric W. Biederman [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=m1pudyr8ju.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=Marcus.Meissner@caldera.de \
    --cc=dilinger@mp3revolution.net \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.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