Jeff Garzik <[EMAIL PROTECTED]> 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
Jeff Garzik [EMAIL PROTECTED] 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
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
>
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
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
Just a warning; I was informed by Alan that doing this for video
drivers was unnecessary, since video devices were already enabled
during bootup.
On Wed, Apr 25, 2001 at 01:06:24PM +0200, Marcus Meissner wrote:
>
> On Wed, Apr 25, 2001 at 09:04:38AM +0200, Marcus Meissner wrote:
> > Hi Alan,
On Wed, Apr 25, 2001 at 09:04:38AM +0200, Marcus Meissner wrote:
> Hi Alan, linux-kernel,
>
> This moves pci_enable_device() in trident.c before any PCI resource access.
> Everything else appears to be ok in regards to 2.4 PCI API and return values.
>
> Ciao, Marcus
Argh, actually the return
Hi Alan, linux-kernel,
This moves pci_enable_device() in trident.c before any PCI resource access.
Everything else appears to be ok in regards to 2.4 PCI API and return values.
Ciao, Marcus
Index: trident.c
===
RCS file:
Hi Alan, linux-kernel,
This moves pci_enable_device() in trident.c before any PCI resource access.
Everything else appears to be ok in regards to 2.4 PCI API and return values.
Ciao, Marcus
Index: trident.c
===
RCS file:
Just a warning; I was informed by Alan that doing this for video
drivers was unnecessary, since video devices were already enabled
during bootup.
On Wed, Apr 25, 2001 at 01:06:24PM +0200, Marcus Meissner wrote:
On Wed, Apr 25, 2001 at 09:04:38AM +0200, Marcus Meissner wrote:
Hi Alan,
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
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
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
13 matches
Mail list logo
