| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Remove x86 specific hacks. Not that they will ever be used on
none x86 arches, but they are built by default. And the way the
flags where added was a hack.
|
|
|
|
|
|
|
|
|
|
|
|
Add the vmwgfx_drm.h header for now, this allows the svga driver
to be enabled by default without forcing people to install the
vmwgfx_drm.h header on their system.
To be removed once vmwgfx_drm.h is in libdrm.
|
|
|
|
This is done by stopping linking to libmesagallium.a and removing DRI
related stuff. The state tracker an application links to decides the
API supported.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
First tri!
|
|
Added a flag if we should send commands to hardware
as what we send isn't all that correct.
|
|
|
|
|
|
|
|
Makes it easier to dump as we get all of the information
about the upload in a single hit.
Opens the window to simplification in the driver if these
relocation arrays can be maintained statically rather than
being recreated whenever we check for a new upload.
Still needs some cleanup to avoid uglyness introduced with the
delta values.
|
|
|
|
The winsys now inserts the presumed offset into referring buffers from
inside of bo_emit_reloc(). Remove the many locally coded places where
this was happening in the driver and eliminate the worry of getting it
wrong.
No longer need to expose offset values to the driver at all, so no need
to worry about what to do in the driver when they change. Just use
zero values wherever we had offsets previously -- the relocations will
fix it all up for us.
|
|
|
|
|
|
|
|
Any allocation that may fail should be checked, and propogate the
error upwards. At the highest level we will flush batch and retry.
This is an alternate strategy to what the original DRI driver did of
attempting to flush batch from the lowest levels (eg inside
BEGIN_BATCH). The trouble with that strategy was that flushes could
occur at unexpected times, and additionally there was a need for a
wierd notification mechanism to propogate the 'lost context' state
back up to higher levels.
Propogating the errors directly gives us a lot of flexibility how to
deal with these states, at the expense of a lot more checking in the
code.
Will add some sanity checks later to make sure that out-of-memory
conditions are properly escalated and not lost halfway up the stack.
|
|
|
|
|
|
But there are some missing symbols, "nm -u i965_dri.so"
[SNIP]
U brw_surface_bo
U brw_surface_pitch
U brw_texture_blanket_winsys_buffer
U brw_texture_get_winsys_buffer
U brw_update_dirty_counts
[SNIP]
|
|
|
|
|
|
|
|
Special case to avoid clutter in the driver
|
|
|
|
|
|
Otherwise xlib state-tracker doesn't know about us.
|
|
Need more linker magic to keep the glX symbols externally visible even
though they started off in a .a file.
|
|
Create a dummy winsys that just debug-prints on calls into the winsys
functions. Will use this to get to the point where we are generating
sane-looking debug dumps and diassembly.
Also fix various warnings generated with the new compiler flags set in
this config.
|
|
Easier to understand what's going on in the driver sources, convert
stereotype usage values back to GEM read/write domain flags in the
winsys.
|
|
|
|
A milestone of sorts. Still a long way from something working --
the old one compiled too, at least some of the time...
|
|
|
|
|
|
The intel_xorg file looks like it's got quite a bit of code that could
be lifted up into the xorg state tracker -- should really just have a
list of pci ids and a pointer to a screen create func.
|
|
I'll want to rework this, not sure trying to share this code is a very
good idea at least until the interfaces from the two drivers calm
down.
|
|
|
|
|
|
|
|
1: add rv530 support
- num z pipes cap
- add proper start/finish query options for rv530
2: convert to use linked list properly.
3: add flushing required check.
4: initial Z top disabling support.
TODO:
make it actually work on my rv530.
|
|
This attempts to make r300g do proper bo space checking as opposed
to whatever it was doing now.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
They now follow the pipe_buffer_write style,
its the gallium driver that sets the interface not
the winsys.
|
|
Very apparent with resizing windows on DRI2.
|
