| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Those functions are SO dead.
|
| |
|
|
|
|
|
|
|
| |
There were several problems with these functions (which are a remnant
of dri1 hyperz mostly - should bring it back somehow someday).
First, it would always do a swrast clear if the buffer to clear was a fbo.
Second, for buffers we wouldn't handle the clear (I guess aux/accum?) we
would actually still have tried to clear that later even when we already
cleared it with swrast.
|
| |
|
|
|
|
| |
The flags which were computed were never actually used.
Reviewed-by: Dave Airlie <[email protected]>
|
| | |
|
| |
|
|
| |
This makes LOCK_HARDWARE empty, so it goes away.
|
| | |
|
| |
|
|
| |
This has been around since the initial import in 2003 and never used.
|
| | |
|
| |
|
|
| |
Only r200 implemented it.
|
| |
|
|
|
|
| |
this moves the emission outside the lock and adds r200 support.
Signed-off-by: Dave Airlie <[email protected]>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
As part of the DRI driver interface rewrite I merged __DRIscreenPrivate
and __DRIscreen, and likewise for __DRIdrawablePrivate and
__DRIcontextPrivate. I left typedefs in place though, to avoid renaming
all the *Private use internal to the driver. That was probably a
mistake, and it turns out a one-line find+sed combo can do the mass
rename. Better late than never.
|
| |
|
|
| |
Only very few places where realy converted so there isa lot of to do.
|
| |
|
|
|
| |
Move all the metaops to a dri_metaops file and port radeon/intel
to use the new common meta ops code.
|
| | |
|
| |
|
|
|
|
|
| |
The duplication of state data caused a crash due to double-free on destruction
of context, because a variable wasn't correctly null'ed out.
Signed-off-by: Nicolai Hähnle <[email protected]>
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Re work depth issues.
Do a lot more FBO abstactions
fixup depth/stencil buffer interactions
|
| | |
|
| | |
|
| |
|
|
|
| |
this is a step towards fbos and should fix pageflipping, but
I think the first flip seems broken.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This merges lots of the hw state atom emission and firevertices code.
it also removes a lot of the extra radeon crap from r300
and merge scissor
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Makefile.template
|
| | |
|
| |
|
|
|
|
|
| |
Instead of passing in a fixed struct, the loader now passes in a list
of __DRIextension structs, to advertise the functionality it can provide
to the driver. Each extension is individually versioned and can be
extended or phased out as the interface develops.
|
| |
|
|
|
|
|
|
| |
* Fix crash at context creation in most drivers supporting vblank.
* Don't pass vblank sequence or flags to functions that get passed the drawable
private already.
* Attempt to initialize vblank related drawable private fields just once
per drawable. May need more work in some drivers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Consolidate support for synchronizing to and retrieving vblank counters. Also
fix the core vblank code to return monotonic MSC counters, which are required
by some GLX extensions. Adding support for multiple pipes to a low level
driver is fairly easy, the Intel 965 driver provides simple example code (see
intel_buffers.c:intelWindowMoved()).
The new code bumps the media stream counter extension version to 2 and adds a
new getDrawableMSC callback. This callback takes a drawablePrivate pointer,
which is used to calculate the MSC value seen by clients based on the actual
vblank counter(s) returned from the kernel. The new drawable private fields
are as follows:
- vblSeq - used for tracking vblank counts for buffer swapping
- vblFlags - flags (e.g. current pipe), updated by low level driver
- msc_base - MSC counter from the last time the current pipe changed
- vblank_base - kernel DRM vblank counter from the last time the pipe changed
Using the above variables, the core vblank code (in vblank.c) can calculate a
monotonic MSC value. The low level DRI drivers are responsible for updating
the current pipe (by setting VBLANK_FLAG_SECONDARY for example in vblFlags)
along with msc_base and vblank_base whenever the pipe associated with a given
drawable changes (again, see intelWindowMoved for an example of this).
Drivers should fill in the GetDrawableMSC DriverAPIRec field to point to
driDrawableGetMSC32 and add code for pipe switching as outlined above to fully
support the new scheme.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Many DRI entry points took a __DRInativeDisplay pointer and a screen
index as arguments. The only use for the native display pointer was to
pass it back to the loader when looking up the __DRIscreen for the given
screen index.
Instead, let's just pass in the __DRIscreen pointer directly, which
let's drop the __DRInativeDisplay type and the getScreen function.
The assumption is now that the loader will be able to retrieve context
from the __DRIscreen pointer when necessary.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The coordinates need to be computed after we've got the hw lock.
Code updated to:
1. Ignore all/x/y/width/height/ params passed to Clear func.
2. Pass 0,0,0,0,0 to _swrast_Clear() until they're totally removed.
|
| |
|
|
| |
request at least drmMinor 6 anyway.
|
| |
|
|
| |
intention as drm seems to never return EAGAIN) in all radeon drivers.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Makes all three drivers use the same screen structure and setup code, with a
few ifdefs for the separate compilation to deal with symbols not being
available to all drivers and the fact that we have no mechanism for dealing
with different config options for different chip families in the same driver.
These issues should be dealt with later.
- Introduces IS_R[123]00_CLASS(radeonScreenPtr) macro for code for taking
different paths depending on the general class of chipset.
- Adds many new R300-class PCI IDs, though not all those listed in
radeon_driver.c.
|
