On Fri, 28 Feb 2014 10:36:59 +0100 Christian König <deathsimple@xxxxxxxxxxx> wrote: > Am 27.02.2014 22:38, schrieb Lauri Kasanen: > > Without this, a bo may get created in the cpu-inaccessible vram. > > Before the CP engines get setup, all copies are done via cpu memcpy. > > > > This means that the cpu tries to read from inaccessible memory, fails, > > and the radeon module proceeds to disable acceleration. > > > > Doing this has no downsides, as the real VRAM size gets set as soon as the > > CP engines get init. > > > > This is a candidate for 3.14 fixes. > > This should be unnecessary, since TTM gets initialized only seeing the > visible VRAM and later on radeon_ttm_set_active_vram_size gets called to > increase the limit. > > If this isn't the case any more we should figure out why instead of > working around it like this. Negative, TTM gets initialized with real_vram just a few lines above this patch, not visible_vram. - Lauri _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
