- 10 Mar, 2010 2 commits
-
-
Marcin Kościelnicki authored
NV50 is nice and has a switch that autoaligns stuff for us. Pre-NV50, we need to align input bitmap width manually. Signed-off-by:
Marcin Kościelnicki <koriakin@0x04.net> Signed-off-by:
Francisco Jerez <currojerez@riseup.net> Signed-off-by:
Ben Skeggs <bskeggs@redhat.com>
-
Marcin Kościelnicki authored
11c/004 offset corresponds to PGRAPH reg 0x400828, and is initialised earlier anyway by both our ctxprog generator and blob ctxvals. It's actually incorrect with the generator, since we use different layout on pre-NVA0. Signed-off-by:
-
- 25 Feb, 2010 25 commits
-
-
Matt Turner authored
CC: Ben Skeggs <bskeggs@redhat.com> Signed-off-by:
Matt Turner <mattst88@gmail.com> Signed-off-by:
-
Ben Skeggs authored
This is in preference to disconnected. If there's no other outputs connected this will cause LVDS to be programmed even with the lid closed rather than having X fail to start because of no available outputs. Signed-off-by: -
Ben Skeggs authored
Not entirely identical to 0x21, the per-encoder table header lacks the third init table pointer. However, our current parsing of the table should work just fine. Signed-off-by: -
Marcin Kościelnicki authored
Signed-off-by:
-
Marcin Kościelnicki authored
This removes dependence on external firmware for NV50 generation cards. If the generated ctxprogs don't work for you for some reason, please report it. Signed-off-by:
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
This makes this code common to both the nv04 and nv50 paths. For the moment, we keep the previous behaviour with HDMI/eDP connectors and report them as DVI-D/DP instead. This will be fixed once the rest of the code has been fixed to deal with those types. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
It's very useful to be able to access this without additional tools for debugging purposes. Signed-off-by: -
Luca Barbieri authored
Found by sparse. Signed-off-by:
Luca Barbieri <luca@luca-barbieri.com> Signed-off-by:
-
Marcin Slusarz authored
i2c_entries seems to be the number of i2c entries, so with index equal to this number, we could read invalid data from i2ctable. Fix it. Signed-off-by:
Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by:
-
Marcin Slusarz authored
Reported-by:
Dan Carpenter <error27@gmail.com> Signed-off-by:
-
Marcin Slusarz authored
get_tmds_index_reg reads some value from stack when mlv happens to be equal to size of pramdac_table array. Fix it. Reported-by:
-
Ben Skeggs authored
This commit breaks the userspace interface, and requires a new libdrm for nouveau to operate again. The multiple GEM_PUSHBUF ioctls that were present in 0.0.15 for compatibility purposes are now gone, and replaced with the new ioctl which allows for multiple push buffers to be submitted (necessary for hw index buffers in the nv50 3d driver) and relocations to be applied on any buffer. A number of other ioctls (CARD_INIT, GEM_PIN, GEM_UNPIN) that were needed for userspace modesetting have also been removed. Signed-off-by:
-
Ben Skeggs authored
This allows us to submit push buffers from any memtype to the hardware. We'll need this ability for VRAM index buffers at some point. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
PFIFO on G80 and up has a new mode where the main ring buffer is simply a ring of pointers to indirect buffers containing the actual command/data packets. In order to be able to implement index buffers in the 3D driver we need to be able to submit data-only push buffers right after the cmd packet header, which is only possible using the new command submission method. This commit doesn't make it possible to implement index buffers yet, some userspace interface changes will be required, but it does allow for testing/debugging of the hardware-side support in the meantime. Signed-off-by: -
Maarten Maathuis authored
The nv50 pgraph handler (for example) could reenable pgraph fifo access and that would be bad when pgraph context is being unloaded (we need the guarantee a ctxprog isn't running). Signed-off-by:
Maarten Maathuis <madman2003@gmail.com> Signed-off-by:
-
- 23 Feb, 2010 6 commits
-
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
This also modifies the unused PRAMIN PT entries to be all zeroes, can't really recall why I used 9/0 initially, just that it didn't work for some reason. It was likely masking a bug elsewhere that's since been fixed. Signed-off-by: -
Ben Skeggs authored
This commit changes nouveau to construct PTEs which look very much like the ones the binary driver creates. I presume that filling multiple PTEs identically with length flags and the physical address of the start of a block of VRAM is a hint to the memory controller that it need not perform additional page table lookups for that range of addresses. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
GART is handled elsewhere, no reason to have the code for it here too. Signed-off-by: -
Francisco Jerez authored
Signed-off-by:
-
- 16 Feb, 2010 2 commits
-
-
Francisco Jerez authored
Signed-off-by:
-
Ben Skeggs authored
Signed-off-by:
-
- 10 Feb, 2010 2 commits
-
-
Matthew Garrett authored
Signed-off-by:
Matthew Garrett <mjg@redhat.com> Signed-off-by:
-
Marcin Slusarz authored
Reported-by:
-
- 09 Feb, 2010 3 commits
-
-
Maarten Maathuis authored
Unset the bit that indicates that a ctxprog can continue at the end. Signed-off-by:
-
Maarten Maathuis authored
ramfc is zero'ed upon destruction, so it's safer to do things in the right order. Signed-off-by:
-
Maarten Maathuis authored
- We need to disable pgraph fifo access before checking the current channel, otherwise we could still hit a running ctxprog. - The writes to 0x400500 are already handled by pgraph->fifo_access and are therefore redundant, moreover pgraph fifo access should not be reenabled before current context is set as invalid. So remove them altogether. Signed-off-by:
-
