public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@mp3revolution.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Marcus Meissner <Marcus.Meissner@caldera.de>,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH: trident , pci_enable_device moved
Date: Wed, 25 Apr 2001 11:24:02 -0400	[thread overview]
Message-ID: <20010425112402.A31842@mp3revolution.net> (raw)
In-Reply-To: <20010425090438.A12672@caldera.de> <20010425130624.A3216@caldera.de> <20010425104949.A31649@mp3revolution.net> <3AE6E797.A31803BE@mandrakesoft.com>
In-Reply-To: <3AE6E797.A31803BE@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Apr 25, 2001 at 11:04:55AM -0400

Oops, I saw "trident" and thought video.  Sorry, marcus.  :)

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)?


On Wed, Apr 25, 2001 at 11:04:55AM -0400, Jeff Garzik wrote:
> 
> Andres Salomon wrote:
> > Just a warning; I was informed by Alan that doing this for video
> > drivers was unnecessary, since video devices were already enabled
> > during bootup.
> 
> To clarify:  the primary display device is enabled and initialized, and
> its video BIOS executed, when during BIOS startup and before the Linux
> kernel gets control.  All other display devices are not only not
> initialized, but they are disabled as well.
> 
> Marcus is doing sound ATM so I doubt this matters to him...
> 
> -- 
> Jeff Garzik      | The difference between America and England is that
> Building 1024    | the English think 100 miles is a long distance and
> MandrakeSoft     | the Americans think 100 years is a long time.
>                  |      (random fortune)
> 

-- 
"... being a Linux user is sort of like living in a house inhabited
by a large family of carpenters and architects. Every morning when
you wake up, the house is a little different. Maybe there is a new
turret, or some walls have moved. Or perhaps someone has temporarily
removed the floor under your bed." - Unix for Dummies, 2nd Edition
        -- found in the .sig of Rob Riggs, rriggs@tesser.com

  reply	other threads:[~2001-04-25 15:24 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 [this message]
2001-04-25 15:35         ` Jeff Garzik
2001-04-27  9:33           ` Eric W. Biederman

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=20010425112402.A31842@mp3revolution.net \
    --to=dilinger@mp3revolution.net \
    --cc=Marcus.Meissner@caldera.de \
    --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