On Sun, May 09, 2004 at 08:14:59PM -0700, Ian Romanick wrote:
| ... I very seriously doubt that you can halt and restart an
| in-progress shader. That would require extra logic, reduce performance,
| and wouldn't help games. What makes you think any of the current cards
| are designed
Holger Waechtler wrote:
Jon Smirl wrote:
Sharing graphics contexts is not the same thing as allowing two
completely
different device drivers access to the hardware on VT swap. Two
different device
drivers may have completely different contents in all of the
registers, CP
running or not, VRAM an
> 1) Keep mode switching in the kernel. Merge DRI and fb together via
>sysfs interface.
>
> 2) Ben suggestion that we mount userland inside the kernel during early
>boot and use a userland library. If we would use a library then it MUST
>be OpenGL. This would be the forced standard
Jon Smirl wrote:
Sharing graphics contexts is not the same thing as allowing two completely
different device drivers access to the hardware on VT swap. Two different device
drivers may have completely different contents in all of the registers, CP
running or not, VRAM and AGP space. With two device
Jon Smirl wrote:
Can you run grub or lilo on these machines?
The equivalent loader is called MILO for SPARC and Yaboot for PowerPC.
The BIOS equivalent is called OpenFirmware and provides a helper API for
mode setting and graphics card initialisation.
There are comments in the drivers which mark
Holger Waechtler wrote:
Jon Smirl wrote:
Can you run grub or lilo on these machines?
The equivalent loader is called MILO for SPARC and Yaboot for PowerPC.
oops -- the SPARC image loader was called SILO. MILO was the mini image
loader for Alpha.
sorry for confusion,
Holger
-
Alan Cox wrote:
On Iau, 2004-05-06 at 20:57, Jon Smirl wrote:
Simple example, DRM starts GPU coprocessor running. VT swap happens. New user
stops coprocessor. VT swap back to DRM. Now DRM thinks it left the coprocessor
running but that's not true now. DRM and FB conflict when FB is using the
copro
Can you run grub or lilo on these machines?
Also, these is no rule saying a device driver can't have several tables of _init
register values that can be used to set the mode on a primary monitor at boot. I
would just like to see all of the code that does DDC decoding and modeline
computations move
On Wed, Apr 28, 2004 at 11:55:45AM +0100, José Fonseca wrote:
> On Wed, Apr 28, 2004 at 10:14:54AM +0200, Felix Kühling wrote:
> > On Tue, 27 Apr 2004 13:35:26 +0100
> > Alan Cox <[EMAIL PROTECTED]> wrote:
> >
> > > Standard problem with Wiki nowdays. Lots of dubious companies have
> > > crawlers
Sharing graphics contexts is not the same thing as allowing two completely
different device drivers access to the hardware on VT swap. Two different device
drivers may have completely different contents in all of the registers, CP
running or not, VRAM and AGP space. With two device drivers you have
10 matches
Mail list logo