The NVIDIA Mac boards I've seen are Mac only. They won't even plug
into a PC because the connector is different. It's like PCI, but has
and extra power tab to drive the Apple Display Connector. None of
those boards have a PC BIOS; they have OpenFirmware fcode.
I think most hardware
On Thu, Aug 25, 2005 at 01:21:55PM -0400, Michael wrote:
Hello,
the attached patch adds DDC2/I2C support to the tdfx driver which has
the distinct advantage to work anywhere since it doesn't depend on the
vbe module. It will try DDC2 first and if that fails fall back to the
old vbe stuff when
Hello,
the attached patch adds DDC2/I2C support to the tdfx driver which has
the distinct advantage to work anywhere since it doesn't depend on
the vbe module. It will try DDC2 first and if that fails fall back to
the old vbe stuff when possible.
Moved mode validation and related stuff
On Tue, 30 Aug 2005, Michael wrote:
the attached patch adds DDC2/I2C support to the tdfx driver which has
the distinct advantage to work anywhere since it doesn't depend on
the vbe module. It will try DDC2 first and if that fails fall back to
the old vbe stuff when possible.
Moved mode
Michael wrote:
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac ( or
other PowerPC boxes )
Wrong. No hardware manufacturer in their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Roberts wrote:
Michael wrote:
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac ( or
On Tue, 30 Aug 2005, Ian Romanick wrote:
Tim Roberts wrote:
Michael wrote:
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac ( or
other
Hello,
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac (
or other PowerPC boxes )
Wrong. No hardware manufacturer in their right
On Tue, Aug 30, 2005 at 06:01:42PM -0400, Michael wrote:
Hello,
I don't see why they should be enabled - they're PC-specific and even
with x86 emulation they would be pretty much useless since you're not
too likely to encounter a graphics board with PC firmware in a Mac (
or other PowerPC
Hello,
Not entirely true. What you say only matters for the primary head,
and only because most manufacturers package only one image (x86, EFI,
OpenFirmware, etc) in their PCI ROMs.
True, but in this case - tdfx - irrelevant. The driver uses vbe only for
monitor ID as far as I can tell, so
Hello,
Is the implication here that plugging a PC PCI graphics card into
a powerpc machine will never work (as a secondary display), even
if the software driving it knows how to initialise it in the absence
of OpenFirmware?
Of course not. All I said is that you're rather unlikely to find a
On Tue, Aug 30, 2005 at 07:06:22PM -0400, Michael wrote:
Hello,
Is the implication here that plugging a PC PCI graphics card into
a powerpc machine will never work (as a secondary display), even
if the software driving it knows how to initialise it in the absence
of OpenFirmware?
Of course
Hello,
Marc appears to have fixed various issues for int10/vbe on non-x86
platforms as part of his sparc work. Perhaps some of those same
issues prevented this stuff from working on powerpc in the past and
so these #ifdef's can be removed now. int10/vbe should fail-safe
on hardware that
On Tue, Aug 30, 2005 at 09:30:26PM -0400, Michael wrote:
Hello,
Marc appears to have fixed various issues for int10/vbe on non-x86
platforms as part of his sparc work. Perhaps some of those same
issues prevented this stuff from working on powerpc in the past and
so these #ifdef's can be
Hello,
Marc appears to have fixed various issues for int10/vbe on non-x86
platforms as part of his sparc work. Perhaps some of those same
issues prevented this stuff from working on powerpc in the past and
so these #ifdef's can be removed now. int10/vbe should fail-safe
on hardware
15 matches
Mail list logo
